Quick start
NEXT integrates with Zapier, allowing you to automate the repetitive tasks of adding/moving Clusters to any of your favorite tools.
Create a Zap in Zapier with Trigger: NEXT AI → New Cluster. Connect your Teamspace, then choose an Action app (e.g., Slack, Jira, Sheets) and map the fields. When Zapier detects a new Cluster in your Teamspace, it will create an item in the target app using your mapped fields (e.g., message, issue, row), with a link back to the Cluster in NEXT AI.
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 Zapier integration
You need a Zapier account for this integration. You can sign up for a free Zapier account at www.zapier.com.
Log in to Zapier (or sign up).
Click Create Zap → in Trigger, search NEXT AI and pick New Cluster.
Sign in to NEXT AI when prompted → choose the Teamspace to connect.
trigger to pull a recent Cluster.
Add an Action app (e.g., Slack) → choose the event (e.g., “Send Channel Message”).
Map fields from the trigger (e.g., Cluster name → title; Cluster URL → source link)
Test and Publish the Zap. Each new Cluster in your Teamspace will now flow to the action app you chose.
Tips
Name Zaps by destination & purpose (e.g., “New Cluster → #customer-insights (Slack)”).
Map the Cluster link into a “source” or “evidence” field so downstream teams can trace the insight back to NEXT AI.
If you need near-real-time behavior, check whether your trigger is instant or polling and adjust plan/intervals accordingly.
Troubleshooting
I can’t find my Teamspace. Reconnect the NEXT AI account within the Zap and ensure you’re selecting the intended Teamspace.
The Zap runs slowly / not immediately. Some triggers are polled at intervals (plan-dependent). Confirm your trigger type and polling settings.
Duplicates appeared in the target app. Review Zap history and apply Zapier’s deduplication guidance (unique IDs, filters, or storage steps).
We hit limits. Complex Zaps have step/field limits, and each successful action consumes tasks from your plan. Keep Zaps concise and monitor usage.
FAQ
Q: What exactly triggers the Zap?
A new Cluster created in the connected teamspace in NEXT AI. That event is the Zap’s trigger.
Q: What fields can I send to my action app?
Use the Zap editor to map fields from the New Cluster trigger (e.g., Cluster name/summary/URL) into the fields of your action app (e.g., issue title, row columns, message text).
Q: Will Zapier include a link back to the Cluster?
Yes—map the Cluster URL into a suitable field (e.g., message body, “source” field), so recipients can trace the insight back to NEXT AI.
Q: My Zap didn’t fire right away—why?
Zapier triggers are either instant (webhook-based) or polling (checked at intervals). If your trigger is polling, expected timing varies by plan and settings.
Q: How do I avoid duplicates?
Use Zapier’s deduplication patterns—e.g., include a unique Cluster ID in your mapping, add a Filter step, or store IDs you’ve already processed.
Q: Will this consume Zapier tasks?
Yes—each successful action step uses a task. Keep an eye on task usage in your Zapier billing/usage area.
Q: Can I route different Cluster types to different tools?
Yes—add a Filter or Paths step based on Cluster attributes, then send each path to a different action app.