Why build something when their is a web services for it? Over the years, more and more web services have offered the ability to add functionalities to the apps we create so that we can focus on the core business. But in doing so, we often find ourselves in a situation where our data is spread across multiple services.
Syncing data manual is tedious and doing direct API integration takes time away from working on the core services of the apps we create. And when we want to sync data between two web services, direct integration is not an option. Until now….
Zapier allows you to sync data between your web app and a web service or even between multiple web services. Want to create a Pivotal Tracker story from a Basecamp todo? No problem. How about a Zendesk ticket from Gmail? Done. Webhook to Trello Card. Simple. Zapier integrates with many web services and it seems like they are adding more all the time.
How it works
A zap is a combination of a trigger and an action. Their dashboard lets you pause, unpause and test your zaps.
- Select Your Trigger: A trigger is the left side of an integration. We watch for the trigger to happen before performing an action. Some examples might be when there’s a new ticket in Zendesk or when there’s a new contact in Highrise.
- Select Your Action: An action is the right side of an integration. An action happens automatically when a trigger is tripped. Some examples are create an issue in GitHub or add a new contact to Google Contacts.
- Build Your Zap: Drag and drop data available from your trigger to create your action. This lets you customize how your action is performed.
- Run Your Zaps: Zapier will periodically run your zaps for you in the background, but you can manually run them from your dashboard.
Give it a try at Zapier.com.