ConnectMachine Zapier integration: setup guide

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

Actions

Trigger speed

Sign-in

You will need

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

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

New Contact

A contact is added to your ConnectMachine account, whether you scanned a card, typed it in, or imported it.

Updated Contact

Any detail on an existing contact changes. Zapier receives the contact’s current values, not just the changed field.

Deleted Contact

A contact is removed. Single deletes, bulk deletes, delete all, and merges can all fire it. Zapier receives one item per deleted contact, including the details captured just before deletion.

Actions

Create Contact

Adds a person or business contact to ConnectMachine from another app. First Name is required for every new contact.

Update Contact

Changes fields on a contact that already exists. Contact ID is required.

Good to know Deleted Contact is a trigger only. There is no Delete Contact action, so a Zap can never delete a ConnectMachine contact on your behalf.

Build your first Zap

Choose your trigger

Add ConnectMachine as the first step and pick a trigger event. This example uses Updated Contact, so the Zap runs every time a contact’s details change.

Pull a sample record

Click Test to load a sample contact. Samples let you map fields before a real event arrives.

Check what the trigger gives you

Expand the sample to see every field you can map into later steps: names, company, job title, primary email and phone, labeled values, locations, tags, and timestamps.

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

Every trigger hands Zapier the full contact record.

What the actions accept

Create Contact and Update Contact take the same set of fields.

Validation rules

Prevent recursive Zaps

When a Zap creates or updates a ConnectMachine contact, that change fires the New Contact or Updated Contact trigger.

Troubleshooting

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

ConnectMachine API reference for Zapier

This reference documents every ConnectMachine API endpoint called by the native integration.