RecordX + Zapier
What it does today
The published RecordX Zapier app is on the roadmap. Today, a Webhooks by Zapier trigger pointed at an outbound URL from RecordX gives you the same effect: every finished meeting fires the URL with the meeting metadata, summary and action items, and downstream Zap steps route it anywhere Zapier reaches. Contact support for the current payload shape and to enable outbound webhooks on your workspace.
Setup today (Webhooks by Zapier)
- Create your RecordX account at recordx.io/register.html.
- In Zapier, create a Zap with Webhooks by Zapier → Catch Hook as the trigger.
- Copy the catch URL Zapier gives you.
- Contact RecordX support and provide that URL - we'll wire the outbound event on your workspace.
- Run a test meeting; Zapier catches the payload and shows the JSON fields.
- Add downstream actions: Slack post, Google Sheets row, Salesforce record, task creation.
Setup (once the published app ships)
- Search "RecordX" in Zapier's app directory.
- Pick a trigger: New meeting, New transcript ready, New action item.
- Connect your RecordX account with OAuth.
- Configure output filters (specific tags, hosts, or projects).
- Add downstream steps.
- Turn the Zap on.
Planned triggers and actions
| Item | Type | Notes |
|---|---|---|
| New meeting created | Trigger | Fires when a recording starts / finishes. |
| Transcript ready | Trigger | Fires when transcription completes. |
| Summary ready | Trigger | Fires when the AI summary lands. |
| Action item extracted | Trigger | One fire per action item - use in loops or filters. |
| Transcribe a file | Action | Submit an audio / video file for transcription. |
| Attach a note | Action | Append a note to an existing meeting record. |
| Tag a meeting | Action | Apply a tag from a Zap - useful for downstream routing. |
Permissions and scopes
The planned Zapier app uses OAuth 2.0. The requested scopes let it read your meetings, transcripts, summaries and action items and post files or notes to your workspace - the same permissions as your own web-app login. You control which workspace the Zap is attached to; you can revoke access from RecordX settings at any time.
Pricing and limits
RecordX doesn't charge extra for Zapier or webhooks. On Zapier's side, Free covers 100 tasks / month and 15-minute polling; Starter and above lift the caps and add multi-step Zaps and shorter polling. Each downstream step in a Zap counts as one task. Volumes for typical meeting cadence stay well within Starter.
Common gotchas
- Webhook payloads are JSON - some downstream apps (older Google Sheets rows) prefer flat key-value; use Zapier's Formatter step.
- 15-minute polling on Free plans means events can arrive up to 15 minutes late.
- Rate limits on downstream apps (e.g. HubSpot's 100 req/10s) can throttle a burst of end-of-day meetings.
- A test event in Zapier requires at least one real meeting in the workspace - use a short throwaway recording.
Alternatives
- Make (Integromat) - same shape via the outbound webhook.
- n8n self-hosted - fine if you'd rather not use a SaaS.
- Direct API calls from your own backend - the RecordX API is the same one Zapier will use.
- Purpose-built native integrations (Slack, HubSpot, Salesforce) once they ship.
FAQ
- Is the Zapier integration live?
- The published Zapier app is on the roadmap. Today you can still wire RecordX to Zapier via a Webhooks by Zapier trigger pointed at an outbound URL RecordX fires on new meeting, or by polling a shared export. Contact support for the current webhook payload shape.
- What triggers and actions are planned?
- Triggers: New meeting, New transcript ready, New action item, New summary. Actions: Transcribe an uploaded file, Attach a note, Tag a meeting. The exact set is not final.
- Which Zapier plan will I need?
- Any Zapier plan including Free. Free covers 100 tasks / month, single-step Zaps, and 15-minute polling. Multi-step Zaps and shorter polling need Starter or above.
- What about Make (Integromat)?
- Make works today via the same webhook mechanism, and the published Make app is planned alongside Zapier. If you have a preference, tell support so we prioritise correctly.
- Do I need to code?
- No. Zaps are click-to-configure. The webhook workaround does require pasting the payload path ("summary.body") into the mapping - the docs walk through it.
Setup checklist
- RecordX account and one recorded meeting for testing.
- Zapier account (Free is enough to prototype).
- Downstream apps identified and their Zapier connectors already authorised.
- Contact support for outbound webhook enablement if you're going the workaround route.
Related integrations
- Slack - a common Zap downstream.
- Notion, Asana, monday.com - all reachable via Zap steps.
- Salesforce, HubSpot - CRM downstream.
- See all integrations.
Sign up free, start transcribing. No credit card required.
Start for free