Content Snare’s Zapier integration enables you to build automated workflows. Zapier connects more than five thousand apps, so you’ll have nearly unlimited possibilities to automate your content collection processes. You should know a few Zapier-related concepts before going through the list of triggers and actions:

  • Zaps are workflows that connect your apps to automate repetitive tasks
  • A trigger is an event that starts a Zap
  • An action is an event a Zap performs

Here’s where you can see more details about Content Snare’s Zapier integration


Request Created 

This fires as soon as you click Add New – Request and before you’ve added a client. We recommend using it to trigger a workflow for when a request has been created via Zapier as a draft.

Request Published 

This fires as soon as the request is published.

Request Completed

This fires when you manually mark a request as complete. It includes all the content that the client has added within the request in response to your questions.

All Fields Completed 

This occurs when all the fields have been marked complete and will only notify you of this.

Client Created

This fires when a new client has been created.

Client Updated 

This fires when a client’s details have been updated.

Field Completed 

This fires when either yourself or a client marks a field as complete. It includes request and client information in order to aid you in identifying which request is concerned.

Field Approved 

This fires when you approve a field. It includes request and client information in order to aid you in identifying which request is concerned.

Field Rejected 

This fires when you reject a field. Much like the previous two triggers, request and client information are included as well as the rejection message given.


Create Request 

This action allows you to create and optionally publish (send) a request. You can create the client, select the desired request template and assign the request a communication template.

Create Client 

This action creates a client. This is recommended only when you wish to create a client without immediately sending them a request. For that, you would instead use Create Request.

App Extensions (Beta)

This performs an API call using an App Extension (Beta) entry that you can select or create later within this Zap’s setup. App Extensions (Beta) can be reused across multiple zaps and are managed centrally through the App Extensions (Beta) builder.

API Request (Beta)

This is an advanced action which makes a raw HTTP request that includes this integration’s authentication. This is useful if an application has an API endpoint that Zapier hasn’t implemented yet. In this case, you are expected to read and utilize the API documentation provided by the application. If the application changes their API, you need to make the appropriate fixes and updates.

Pro tip: Learn how to automate your business to create more free time with Zapier Mastery

Next steps:

Updated on March 24, 2024

Was this article helpful?

Related Articles