Content Snare’s Zapier integration enables you to build automated workflows. Zapier connects more than five thousand apps, so you\u2019ll 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:<\/p>\n\n\n\n
Here\u2019s where you can see more details about Content Snare\u2019s Zapier integration<\/a>. <\/p>\n\n\n\n This fires as soon as you click Add New \u2013 Request and before you\u2019ve added a client. We recommend using it to trigger a workflow for when a request has been created via Zapier as a draft.<\/p>\n\n\n\n This fires as soon as the request is published.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n This occurs when all the fields have been marked complete and will only notify you of this.<\/p>\n\n\n\n This fires when a new client has been created.<\/p>\n\n\n\n This fires when a client\u2019s details have been updated.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n This fires when you approve a field. It includes request and client information in order to aid you in identifying which request is concerned.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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.<\/p>\n\n\n\n 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\u2019t 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.<\/p>\n\n\n\nTriggers<\/h2>\n\n\n\n
Request Created <\/h3>\n\n\n\n
Request Published <\/h3>\n\n\n\n
Request Completed<\/h3>\n\n\n\n
All Fields Completed <\/h3>\n\n\n\n
Client Created<\/h3>\n\n\n\n
Client Updated <\/h3>\n\n\n\n
Field Completed <\/h3>\n\n\n\n
Field Approved <\/h3>\n\n\n\n
Field Rejected <\/h3>\n\n\n\n
Actions<\/h2>\n\n\n\n
Create Request <\/h3>\n\n\n\n
Create Client <\/h3>\n\n\n\n
App Extensions (Beta)<\/h3>\n\n\n\n
API Request (Beta)<\/h3>\n\n\n\n
Pro tip<\/strong>: Learn how to automate your business to create more free time with Zapier Mastery<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Next steps:<\/h3>\n\n\n\n