Closing the Loop with Zapier!

Amazing Things with Zapier

Imagine if you could launch a checklist run in Manifestly for each new Zendesk support ticket your company receives and then update that support ticket once the checklist is completed.

The are two main ways to use Zapier with Manifestly.

1. You can launch a checklist when an event happens in another web service you utilize.

1. You can also update another system when a checklist is completed.

Zapier calls the difference between these two flows actions and triggers.

Close The Loop

With these two processes we can now close the loop between Manifestly and any other system.

An example of this would be a support ticket in Zendesk. Some of our customers utilize Manifestly to implement extra workflow on their tickets via the following process:

1. A new support ticket is created in Zendesk
2. This new ticket creates a checklist run (automatically via Zapier) in Manifestly
3. That checklist run is worked on by the participants
4. They finish the checklist
5. The original support ticket is updated (automatically via Zapier!)

How to Make these Zaps

The glue that connects these apps is the ID of your original record — in this example, it is the ID of the support ticket. That ID is sent to the external ID of your checklist run in Manifestly.

There are 3 main steps to configuring your Zaps.

1. Utilize the external ID when creating the original checklist run in Manifestly.
2. Use this external ID to search for the original zendesk ticket
3. Update that ticket to the appropriate status

A screenshot of setting up the original Zap to create the checklist run.

Searching for the original support ticket using the ID.

Once you have this set up, you can update that original record in whatever way you want. Close the ticket, set it to a different status, add a comment…

That’s it! Zapier is workflow glue and you can connect all sorts of apps to Manifestly and Manifestly back to those apps. Any questions, please contact us! philip@manifest.ly