Check this article to find out how to connect third-party applications with Holded via Zapier.
The Zapier integration allows you to connect Holded to a great variety of apps for your daily use. Applications get connected via API, without any coding effort, allowing you to achieve more effective time management, by accessing and leveraging information in a more immediate way and from a single place.
Please note that the maintenance of the previous version of this integration will be discontinued.
Information and applications you can work with
From Zapier you have the option to use the workflow templates or Zaps that we have elaborated for you to transfer data from your third-party application to Holded. The good thing about templates is that we have gathered a great number of frequent apps used by our customers, and we have already provided you with all the logic to transfer information from one platform to another.
The only action required when using the templates is to authenticate in both the applications you connect. Note that predefined workflows can be checked and modified on your end if you wish to.
The good thing about this integration is that you are not only limited to templates. You can also create your own Zaps to connect to any other app available on Zapier.
When it comes to the kind of data that you can send automatically from one platform to another, you can currently transfer information about: Contacts, Deals, Employees, and Documents (sales invoices, purchase invoices, quote, sales orders, sales receipts).
What are Triggers and Actions in Zaps?
As we said before, by creating Zaps you can move information between platforms, but how do they exactly work?
Zaps need events called Triggers and Actions to work. A trigger is an event that starts a Zap. Once you've set up a Zap, Zapier will monitor for that trigger event. For example, let’s say that you want to create a new contact in Holded every time a new contact is created in Hubspot. In this case, the trigger is the creation of a new contact in Hubspot, so we can say that the trigger is the condition that makes the whole process start. Actions, on the other side, are what happens after the trigger takes place. In the previous example, the action is the new contact created in Holded. In a way, we can understand the actions as consequences.
Zaps always require exactly one trigger which can be combined with one or more actions, the latter case is known as multistep workflows.
Note that Zapier users need a paid account to build multistep workflows
Keep in mind that we are constantly building additional actions and triggers to offer you more ways of moving information between third-party apps and Holded.