Skip to main content

Automations

Owners and admins with a verified email can send demo contacts, named recipient activity and quiz submissions to independent connections. The existing lead webhook remains separate. Each connection has its own address, events, signing secret and history; an organization can keep up to 50 connections.

Automations

Create a connection​

Create a receiver in Zapier, Make, n8n or your service first. Its final HTTPS endpoint must be publicly reachable; private-network addresses and redirects are rejected.

  1. Open Integrations in Organization settings, open Automations and select Add connection.
  2. Choose your Automation tool to see where it provides the endpoint address.
  3. Enter a Connection name and the Endpoint URL, and choose the Events to send.
  4. Keep Send events on and select Add connection in the dialog.
  5. Open the new connection, choose a Sample event and select Send test event. Check the result under Recent deliveries and in your receiver.

Edit connection opens the same dialog. Pausing Send events does not backfill events that happen during the pause. Remove connection cancels waiting deliveries for this connection.

Events and deliveries​

New contact sends a contact form submission. Recipient opened and Recipient finished each report the first corresponding activity for a recipient link, once per link. They do not identify anonymous viewers. Recipient email may be empty. Quiz submitted sends each submitted quiz with the name and email entered, the score and every answer. An answer awaiting a manual grade has no result, and a later grade is not sent.

Send samples to a test destination first: they contain fictional details and synthetic: true, but can still trigger actions in the receiver. Filter synthetic events before real business actions.

Events leave within seconds. Each connection receives its own events in order, and a slow receiver does not delay the others. Recent deliveries shows attempts and results. A delivered status means the receiver accepted the request, not that later CRM or email actions succeeded. Failed requests retry after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. Deduplicate retries by the unchanged event id. Copy secret copies this connection’s secret; Rotate secret changes it immediately, so update the receiver. See signature verification.

Generic Zapier setup uses Webhooks by Zapier → Catch Hook, which requires a paid Zapier plan. Use Catch Raw Hook or a raw-body receiver for signature verification. Make uses a Custom webhook plus the included manual recipes. The n8n JSON workflows include HubSpot contact upsert and Google Sheets contact/followup upserts; select your credentials and resources before activation. Sheets updates match event IDs, but concurrent inserts can race. The kit README explains verification and retry handling.

Choose Download automation starter kit in the application’s Integrations settings.

Native Zapier app​

The Demo-Creator app for Zapier offers New Contact, Recipient Link Opened, Recipient Link Completed, New Quiz Submission and Create Recipient Link. Choose Open in Zapier under Integration credentials and connect the app with a credential from this organization; it needs no connection under Automations. Until Zapier finishes its review, the button opens an invitation instead of the Zapier App Directory. Returned demo links can use your connected domain.

Integration credentials​

  1. On the same Integrations tab, open Integration credentials and select Create credential.
  2. Enter a Credential name and choose Expires after. Under Permissions, every permission is selected at first; clear the ones the tool does not need.
  3. Select Create credential, then Copy credential. It cannot be displayed again.
  4. Store it in the automation tool’s credential settings.
  5. After the tool’s first request, check that the saved credential shows when it was last used.

Each credential applies to one organization and only its selected permissions. Each saved credential shows when it expires or expired. An organization can keep up to 50 credentials that have not expired.

Triggers require Read event samples and verify deliveries and Manage its own event subscriptions. The recipient-link action requires Create recipient links; its demo selector also requires List published demos. Use a stable upstream record ID in the action’s idempotency field to reuse the same result on retries.

Revoke credential stops API access and removes subscriptions created by that credential. Expired credentials stop working. Credentials issued through SSO cannot outlive the issuing SSO session; session expiry or logout can stop them earlier than the selected duration.