Quick start

Use Zapier when your source tool doesn’t yet have a native NEXT AI integration (we already support popular apps like Gong, Zoom, Intercom, Zendesk, and many others). Create a Zap with a Trigger from your source app (e.g., “New file in folder” or “New ticket”), then add an Action: NEXT AI → Create Recording (Zapier’s event name). Choose your Teamspace, map either a downloadable file URL (audio/video/text) or plain text, add a title/description/labels, then Test and Publish.

Why use Zapier

Zapier connects thousands of tools with a simple trigger → action model. Using New Cluster as the trigger lets you push validated customer themes from NEXT AI into the tools where teams plan and act—without writing code.

How to set up

Create Zap → In Trigger, pick your source app and event (e.g., “New file in folder,” “New ticket,” “New response”).
Sign in to the source app if prompted → Test trigger to pull a sample.
Add Action: NEXT AI → choose Create Recording (Zapier event name) → Continue.
Sign in to NEXT AI (if you use a custom domain like yourcompany.nextapp.co, enter it when prompted).
Configure the action:
- Teamspace: choose where to create the item
- Import URL or Import text: map your file URL (direct download) or plain text payload
- Title / Description / Labels: map fields from your trigger
Test the action → Publish your Zap. New items then appear automatically in the selected Teamspace.

File inputs in Zapier actions accept a file object or a URL that directly serves the file (public or time-limited signed links).

What gets created in NEXT AI

Object created: A new data item in the Teamspace you select (created by Zapier’s “Create Recording” action).
Included fields: your title, description, labels, and either imported file via URL (audio/video/text) or imported text.
Traceability: include the source app’s URL/ID in the description so teammates can trace back to origin.
Details reflect the current Zapier action configuration for NEXT AI.

Tips

Use it when there’s no native app: check our Integrations & MCP section first; prefer native connectors for Gong, Zoom, Intercom, Zendesk, etc.
Keep titles scannable; push long context into description.
Map a stable source ID (ticket ID, file ID) into description/labels for dedupe and audit.

Troubleshooting

My Zap didn’t fire immediately. Some triggers are polled (not instant) and run at intervals by plan/settings. Check your trigger type and polling cadence.
The file didn’t import. Ensure you mapped a direct download URL (or sent a file object) and that the link isn’t blocked by login pages.
Duplicates appeared. Use Zapier’s deduplication patterns—map a unique ID, add a Filter step, or track processed IDs to prevent re-creates.

FAQ

Q: When should I use Zapier vs a native integration?

Use Zapier for tools we don’t natively support. If we have a native integration (e.g., Gong, Zoom, Intercom, Zendesk), prefer that for simpler setup and richer mappings.

Q: What kinds of data can I import?

Audio and video via file URL, or plain text (e.g., ticket body, survey response). Map either Import URL or Import text in the action.

Q: Does the file URL need to be public?

Zapier actions accept a directly downloadable link. Many teams use time-limited signed URLs from storage apps; avoid links that require interactive login.

Q: The Zap is slow / delayed—normal?

If your trigger is polling, Zapier checks for new data on a schedule (interval depends on plan and trigger). For near-real-time, use instant triggers where available.

Q: How do I prevent duplicates in NEXT AI?

Include a unique source ID (e.g., ticket ID) in labels/description, and follow Zapier’s dedupe guidance to ensure a given source item only creates one data item.