Automate data flow between Clarify and 7,000+ apps without writing code. Use Zapier to create records, sync data, send notifications, and trigger actions when things change in Clarify.
Connecting Zapier
Clarify's Zapier integration is on version 2.0.0, which uses WorkOS for authentication.
To create a new connection:
Go to Zapier and search for "Clarify"
Click Connect to start the authentication flow
Sign in with your Clarify credentials (via WorkOS)
Enter your workspace slug when prompted (e.g.,
acme— not "Acme Inc.")
Each Zapier connection works with one workspace only. If you use multiple workspaces, create separate connections for each.
Migrating from an older connection: Existing connections from before June 2025 will continue to work temporarily. You'll need to create a new connection using the updated authentication before the migration deadline (communicated separately). Your Zaps have already been migrated to the new app version — only the connection needs to be recreated.
Available triggers
Triggers start your Zap when something happens in Clarify.
Trigger | Description |
New Record Created | Fires when a Person, Company, or Deal is created |
Record Added to List | Fires when a record is added to a Clarify list |
Record Updated | Fires when an existing record is updated |
Available actions
Create and update
Action | Description |
Add Label to Record | Add labels to a record |
Create Comment | Add a comment to any record |
Create Record | Create a Person, Company, or Deal |
Delete Record | Delete a record |
Get Meeting Recording Transcript | Retrieve a meeting transcript |
Remove Label from Record | Remove labels from a record |
Update Record | Update an existing record |
Search
Action | Description |
Find Company | Search by domain name (optionally create if not found) |
Find Person | Search by email, name, or LinkedIn (optionally create if not found) |
Find User | Search workspace users by email or phone |
Find Meeting | Search by meeting ID |
Find Record | Search by record ID |
Getting meeting transcripts
To send meeting transcripts to another tool:
Create a Zap with trigger Record Updated → object type Meeting Recording
Add a Filter step: Transcription S3 Key → exists
Add action Get Meeting Recording Transcript
Map the transcript to your destination (Slack, Google Docs, etc.)
Using custom fields
Custom fields are not included in trigger payloads. To access custom field values in your Zap, add a Find a Record action step using the record ID from the trigger, then reference the custom fields from that step's output.
Known limitations
Custom fields not in triggers — must use a Find action to access them
Date fields — must be in ISO 8601 format (
YYYY-MM-DD) or updates fail silentlyCompany field on People — expects the Company ID (a GUID), not the company name. Use Find Company first to get the ID.
No Find Deal action — cannot search for deals by name. Use the record ID if known.
Single workspace per connection — multiple workspaces require separate connections
Troubleshooting
Issue | Fix |
Zap fails with "Record not found" | Enable "Continue if no results" in the Find step, or add a Filter to check first |
Connection errors after auth change | Create a new v2.0.0 connection and update your Zaps to use it |
Custom fields missing from trigger data | Add a Find Record action step to retrieve them |
Internal server error on Deal creation | Check for missing required fields (name, company), invalid company ID, or stage values that don't match your pipeline |
Date fields not updating | Use ISO 8601 format: |