Connect ConnectMachine to Zapier

Send every new and updated contact from ConnectMachine straight into the apps you already use, and write contacts back from those apps. This guide walks through connecting your account, the triggers and actions you get, the fields you can map, and how to fix the problems people run into most.

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.

What you are approving

• Read your account details
• Read contacts and networks
• Create and update contacts
• Manage its own trigger subscriptions

Disconnecting

To revoke access, open My Apps in Zapier, find ConnectMachine, and remove the connection. Zaps that use it stop running until you connect again. Reconnect the same way if your plan changes or a security check closes the connection.

Triggers and actions

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

Triggers

1. New Contact: A contact is added to your ConnectMachine account, whether you scanned a card, typed it in, or imported it.
2. Updated Contact: Any detail on an existing contact changes.
3. Deleted Contact: A contact is removed.

Actions

1. Create Contact: Adds a person or business contact to ConnectMachine from another app. First Name is required for every new contact.
2. Update Contact: Changes fields on a contact that already exists.

Good to know: Deleted Contact is a trigger only. There is no Delete Contact action.

Build your first Zap

Choose your trigger

Add ConnectMachine as the first step and pick a trigger event. This example uses Updated Contact.

Pull a sample record

Click Test to load a sample contact.

Check what the trigger gives you

Expand the sample to see every field you can map into later steps.

Map fields into the next app

Add your second app and drag ConnectMachine fields into it.

Handle deletions

Use the Deleted Contact trigger to keep other systems tidy.

Fields you can map

What a trigger gives you

• Item ID: Stable ID for the event.
• Contact ID: The ConnectMachine contact ID.
• Event Type: Whether the contact was created, updated, or deleted.
• Source: Where the change came from.
• First Name, Last Name, Company: Core identity fields.
• Created At, Updated At, Deleted At: Timestamps in UTC.

What the actions accept

• Contact ID: Required when updating.
• First Name: Required when creating any contact.
• Primary Email, Primary Phone, Website: Optional updates.

Prevent recursive Zaps

When a Zap creates or updates a ConnectMachine contact, that change fires the appropriate trigger. To avoid loops, add a filter to ignore changes made by your own Zaps.

Troubleshooting

• Zapier says your plan does not include Zapier access: Renew your paid subscription.
• A step fails asking you to reconnect: Reconnect ConnectMachine in Zapier.
• An action reports that the contact could not be found: Check the Contact ID.

ConnectMachine API reference for Zapier

Authentication and scopes

The integration uses OAuth 2.0 authorization. Protected endpoints require Authorization: Bearer <access_token>.

Endpoints

OAuth 2.0 with PKCE

• GET /api/v1/oauth/authorize: Starts authorization.
• POST /api/v1/oauth/token: Exchanges an authorization code for an access token.

Instant trigger subscriptions

• POST /api/v1/zapier/subscriptions: Subscribes to contact events.
• DELETE /api/v1/zapier/subscriptions/{id}: Removes trigger subscription.

Contact actions

• POST /api/v1/zapier/contacts: Creates a contact.
• PATCH /api/v1/zapier/contacts/{id}: Updates a contact.

Error response

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