Redacto × Zapier — Setup Guide

What And Why?

Prerequisites • A Zapier account with the right plan for multi-step Zaps (A Zap is Zapier jargon for an automation workflow ) and any premium apps you plan to use. On free plans, multi-step Zaps and premium apps can’t be published. 

• Your Redacto CMS API Key (how to get it: see Appendix).

• Access to Slack/Gmail/Mailchimp (or whichever apps you’ll use in the downstream steps).

• To start with creating Zaps, an organization and workspace should be configured for the redacto Consent Management System.

Note: If you don’t see Redacto in Zapier’s app directory yet, the app may still be in public beta. Ask your Redacto admin for the invite link while we’re in beta; after ~90 days apps graduate to public listing. 

Detailed Tutorial

1. Create a new Zap

   1. Sign in to Zapier.
   2. Click Create → Zaps to open the Zap editor. • You’ll configure a trigger (what starts the Zap) and actions (what happens next).
   
   
   

2. Connect Redacto (API Key authentication)

   1. In the Trigger step, search for Redacto.

   2. In the Account field, you can select which Redacto account you want to proceed with. This can either be an old account or you can click "+ Connect a new account".

   3. When prompted, paste your CMS API Key and complete the connection.

   
   
   
   

3. Choose a Redacto trigger
   1. In Trigger event, select one of: • Grant Consent • Revoke Consent Each trigger represents a specific consent event type.
   2. Configure any required fields for the trigger in Configure (fields with * are required) in the nest s

4. Select a Purpose
   1. Redacto consents are scoped to resources called Purposes. Use the Configure tab to choose the exact Purpose to monitor. Subsequent runs of this Zap will only fire for consent events on this Purpose.
   2. You can see all the purposes configured in your organization listed here with their unique IDs.
   3. From this list, you can select purpose or a set of purposes and continue to the test tab. You can refer here for steps to configure a Zap with multiple purposes.

5. Test the trigger i. Click the Test tab → Test trigger. Zapier will load one or more records that represent your Redacto consent events on the previously selected purposes.

6. Add action steps (Slack, Gmail, Mailchimp — examples)
   1. After the trigger, add one or more actions to complete the workflow.  Example A — Slack: post a channel message
   2. Click + to add an Action → search Slack → Send Channel Message.
   3. Connect your Slack account when prompted.
   4. In Message Text, map Redacto fields from the trigger (e.g., purpose_name, consent_status, subject_email).
   5. Test step (Zapier will post a real message to the chosen channel). Example B — Gmail: send an email
   6. Add Gmail → Send Email.
   7. Connect Gmail.
   8. Map To, Subject, Body from trigger fields (e.g., send a notice when consent is revoked).
   9. Test step to send a live test email. Example C — Mailchimp: add/update subscriber
   10. Add Mailchimp → Add/Update Subscriber.
   11. Connect Mailchimp.
   12. Map Subscriber Email and optional fields/tags from Redacto fields (e.g., tag audience members by Purpose).
   13. Test step to create/update a contact.

7. Publish the Zap

   1. Click Publish (top right). After publishing, Zapier actively monitors the Redacto trigger and runs the action steps whenever the event occurs. You can confirm the publish status of your zap through the toggle on the top left corner of Zapier's editor -
   

   PS: Zaps only trigger on new data after publish—historical events do not backfill runs.

Appendix

A) How to get a CMS API Key?

B) Steps to configure a Zap with multiple purposes.

C) Monitor runs & troubleshoot