Connect ConnectMachine to Zapier

Before you start

The ConnectMachine app on Zapier gives you three triggers and two actions for your contacts. Triggers are instant, so a Zap runs within seconds of a contact changing instead of waiting for a polling interval.

Triggers

New, Updated, and Deleted Contact

Actions

Create Contact and Update Contact

Trigger speed

Instant. No polling delay

Sign-in

No password or API key needed

You will need

• A ConnectMachine account with onboarding finished.
• Zapier access on your ConnectMachine plan: a paid subscription, a seat on an organization license, or an active Premium trial.
• A Zapier account. Zapier’s free tier includes 100 tasks per month, which is enough for most single-step Zaps.

Connect your account

You connect ConnectMachine to Zapier once. After that, every Zap you build can reuse the same connection.

1. In Zapier, create a Zap and search for ConnectMachine.
2. Pick a ConnectMachine trigger or action, then click Sign in.
3. ConnectMachine opens a consent page. Sign in with Google or with a code sent to your email. You are never asked for a password.
4. Review the permissions you are granting, then click Approve and continue.
5. Zapier returns to the Zap editor with your ConnectMachine account connected and ready to use.

Click to enlarge

What you are approving

Triggers and actions

Triggers start a Zap when something happens in ConnectMachine. Actions let another app write into ConnectMachine.

Triggers

Actions

Build your first Zap

This walkthrough keeps a Google Sheet and ConnectMachine in step with each other. The same pattern works for any of the apps Zapier connects to.

Click to enlarge

Click to enlarge

Click to enlarge

Click to enlarge

Click to enlarge

Looking for ideas? The ConnectMachine on Zapier page lists popular Zaps for Salesforce, HubSpot, Slack, Gmail, and Airtable.

Fields you can map

What a trigger gives you

Every trigger hands Zapier the full contact record, so you can map any of these into a later step.

What the actions accept

Create Contact and Update Contact take the same set of fields. Fill in only the ones you want to set.

Validation rules

• Email values must be valid email addresses.
• Website, social, and map links must start with http:// or https://.
• Latitude must be between -90 and 90. Longitude must be between -180 and 180.
• Blank fields are ignored. Update Contact never clears a value by leaving the field empty.
• The contact and network you pick must belong to the connected ConnectMachine account.

Prevent recursive Zaps

When a Zap creates or updates a ConnectMachine contact, that change fires the New Contact or Updated Contact trigger like any other change. If the same Zap listens for those triggers, it can set itself off again in a loop.

Every trigger record carries a Source field. Changes made by your own Zaps arrive with a source of zapier, so you can filter them out.

You only need this on Zaps that write back into ConnectMachine. A Zap that just sends contacts out to another app cannot loop.

Troubleshooting

Most problems come down to the connection, your plan, or a value that failed validation. Find the symptom below.

ConnectMachine API reference for Zapier

This reference documents every ConnectMachine API endpoint called by the native integration. These are production HTTPS endpoints; the integration does not call a sandbox, test, stage, or development API.

Authentication and scopes

The integration uses OAuth 2.0 authorization code flow with PKCE. Protected endpoints require Authorization: Bearer <access_token>. Zapier requests the scopes user:read, contacts:read, contacts:write, and webhooks:write.

{
  "access_token": "<access-token>",
  "refresh_token": "<refresh-token>",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "user:read contacts:read contacts:write webhooks:write"
}

Endpoints

Contact mutation JSON

Create Contact and Update Contact accept JSON with the following fields. Unknown fields are ignored. Blank values do not clear existing data.

Instant trigger delivery

ConnectMachine sends one HTTPS POST to the subscription target URL. Created and updated events include current contact snapshots. Deleted events include contact_ids and, when available, the pre-delete snapshots in contacts. Zapier turns each contact into one trigger item whose Item ID combines the event and contact IDs.

{
  "event_id": "event_01",
  "occurred_at": "2026-08-04T12:00:00Z",
  "source": "app",
  "source_id": "contact_01",
  "data": {
    "event_type": "contacts.updated",
    "contacts": [{
      "id": "contact_01",
      "type": "person",
      "first_name": "John",
      "last_name": "Doe",
      "primary_email": "john.doe@example.com",
      "updated_at": "2026-08-04T12:00:00Z"
    }]
  }
}

Errors

Errors use a consistent JSON body. A 429 response also includes a Retry-After header.

{
  "error": "invalid_request",
  "error_description": "Invalid contact payload"
}