Native Zapier integration

ConnectMachine’s native Zapier integration

Build instant, two-way contact workflows without copying webhook URLs. Connect once, choose a trigger or action, map the fields, and publish your Zap.

Available to active paid subscribers, organization license members, and active Premium trials.

Triggers and actions

The integration contains five visible operations.

New Contact trigger — runs for contacts.created.
Updated Contact trigger — runs for contacts.updated.
Deleted Contact trigger — runs for contacts.deleted and includes the contact snapshot captured before deletion.
Create Contact action — creates a person or business contact.
Update Contact action — updates an existing contact selected from a dropdown or mapped as a custom ID.

Important

Deleted Contact is a trigger only. There is no Delete Contact action.

Connect your account

Choose ConnectMachine in Zapier and click Sign in. Approve access using Google or an email verification code. Only an existing, onboarded ConnectMachine account can connect. Reconnect from Zapier if your authorization is revoked or a refresh-token security check closes the connection.

Create Contact fields

Choose person or business, then map first name, last name, company, job title, notes, an optional network, primary email, primary phone, and website.

Person contacts require a first name.
Business contacts require a company.
Email and website values are validated.
If Network is omitted, ConnectMachine uses your default network.

Update Contact fields

Contact ID is required. Pick a recent contact from the dropdown or choose Custom to map an ID from a previous Zap step. Map only the fields you want to change.

Blank or omitted values do not clear data in v1.
Primary email, phone, and website update the current primary value or create one.
The selected contact and network must belong to the connected account.

Prevent recursive Zaps

Changes created by ConnectMachine actions emit the normal New Contact or Updated Contact trigger. Their output contains source=zapier and source_id for the connection grant.

Important

Add a Zapier Filter such as “source does not exactly match zapier” when a Zap writes back to ConnectMachine.

Deleted contacts

Deleting one contact, bulk deleting, delete-all, or merging contacts can run the Deleted Contact trigger. Zapier receives one item per deleted contact with deleted_at and its pre-delete fields. The older manual webhook integration remains ID-only for deletion events.

Privacy and permissions

Zapier stores the OAuth credentials for your connection. ConnectMachine stores only access-token identifiers and hashed refresh tokens. The consent page never stores either token in browser storage.

user:read labels the connection.
contacts:read powers triggers, samples, and dropdowns.
contacts:write permits Create Contact and Update Contact.
webhooks:write lets Zapier manage only its own trigger subscriptions.

Developer reference

OAuth uses authorization code with S256 PKCE and automatic refresh. Native subscriptions use POST /api/v1/zapier/subscriptions and DELETE /api/v1/zapier/subscriptions/:id. Trigger samples use GET /api/v1/zapier/trigger-samples. Actions use POST /api/v1/zapier/contacts and PATCH /api/v1/zapier/contacts/:id.

Troubleshooting

A Premium message means the account no longer has an eligible plan. A permission message means the Zap needs to reconnect and approve the requested scopes. If a trigger stops after Zapier returns 410 Gone, turn the Zap on again so Zapier creates a fresh subscription. For repeated authentication errors, remove the connection in Zapier and reconnect.