Zapier: Difference between revisions
From Planfix
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
Zapier generally works as follows: | '''Zapier generally works''' as follows: | ||
*an event occurs in one service; | *an event occurs in one service; | ||
*information about it is sent to Zapier; | *information about it is sent to Zapier; | ||
*Zapier performs a certain action in another service according to rules that have been set up. | *Zapier performs a certain action in another service according to rules that have been set up. | ||
The logic for interaction between services must be configured in Zapier. Here is how that is done: | |||
*select an event (a TRIGGER) that occurs in Service 1; | |||
*indicate something (an ACTION) that should happen in Service 2 as a result of the event; | |||
*a SEARCH can be used to find the desired object in Service 2. | |||
Planfix can be either Service 1 or Service 2. Planfix supports a specific set of events and actions. |
Revision as of 04:06, 18 March 2019
Zapier is a service that automates routine operations, which are usually related to data exchange between services.
Many services are integrated with Zapier; you can exchange data with the following:
Zapier generally works as follows:
- an event occurs in one service;
- information about it is sent to Zapier;
- Zapier performs a certain action in another service according to rules that have been set up.
The logic for interaction between services must be configured in Zapier. Here is how that is done:
- select an event (a TRIGGER) that occurs in Service 1;
- indicate something (an ACTION) that should happen in Service 2 as a result of the event;
- a SEARCH can be used to find the desired object in Service 2.
Planfix can be either Service 1 or Service 2. Planfix supports a specific set of events and actions.