- Home
- Resources
- Integrations
- Not Diamond
Not Diamond Zapier integrationAutomate Not Diamond with Zapier.
The Not Diamond Zapier integration has 0 triggers, 1 action and 0 searches. That one action, Route Prompt, takes a prompt and tells you which AI model, among those you list, should answer it. Another app starts the Zap; Not Diamond picks the model.
Verified Trustpilot reviews · AI, automation & growth agency
What the Not Diamond Zapier integration does
Not Diamond is a model router: you give it a prompt and a list of large language models (LLMs, the engines behind AI assistants), and it answers with the label of the one it recommends. On Zapier it offers a single action, Route Prompt, so it always sits in the middle of a Zap, never at the start.
Three results people build with it. A model choice per request: a form question or a support message goes through Route Prompt, and the label it returns decides which AI step runs next. A cost-aware split: you list a cheaper model and a stronger one, and only the prompts Not Diamond sends to the stronger one reach it. A routing log: each label goes into a spreadsheet next to the prompt, so you see which model gets which kind of question before you commit to a setup.
What Zapier does not do here is worth knowing upfront. Route Prompt returns a label, not an answer: calling the chosen model is a separate step in another app, and the routing alone writes nothing for the reader. Not Diamond has no trigger, so nothing inside it can start a Zap, and no search. Sending each label to the right model means a filter or several branches, which makes the Zap multi-step and puts it on a paid plan.
For a wider view of AI automation tools, our n8n vs Zapier comparison lays the criteria side by side.
Zapier vocabulary in one minute
Seven words cover this page. Each keeps the meaning given here from now on.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Not Diamond has none, so the trigger always comes from another app.
- Action
- What the Zap does once started: the step that writes, sends or moves something. Route Prompt is one, returning a model label.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Each Route Prompt that works counts as one.
- Polling vs instant
- A polling trigger is checked on a timer; an instant one is reported by its app as it happens. The other app's trigger decides which.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, for example a given model label.
- Connection
- Your Not Diamond account linked to Zapier once, then reused by every Route Prompt step you add.
What a Not Diamond Zap really costs
Not Diamond is not a premium app, so it works on the free plan. The trigger of the other app costs nothing; each Route Prompt that succeeds costs one task.
- Trigger (other app)0 tasks
- Each Route Prompt1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A form feeding Route Prompt fits, but then the label goes nowhere useful. Calling the chosen model afterwards is a second action, and a filter on the label is another step, so a working routing Zap is multi-step and needs a paid plan. Every successful action is billed on its own: route plus answer is two tasks per prompt. The grid below concerns the polling trigger of the other app, if it is one.
Connect Not Diamond to Zapier in 3 steps
- 01
Open your apps
In Zapier, go to the Apps page of your account and click + Add connection. You need a Not Diamond account before you start, and its sign-in details at hand for the next step.
- 02
Pick Not Diamond
Type Not Diamond in the search box of the dialog, select it, then click Add connection. A new tab opens on the Not Diamond side to start the link with your account.
- 03
Sign in and allow access
Sign in to Not Diamond in that tab and grant Zapier access to the account. The connection is saved once, and every Route Prompt step reuses it afterwards.
Your first Zap: let Not Diamond pick the model for each question
GoalEach time a customer submits a question through a form, ask Not Diamond which model fits, and only send it to the stronger model when that is the label.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose your form tool and its new entry event as the trigger, connect the account and select the form that collects questions.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent entries, so you map from a real question. If the form is new, submit one test entry first.
- 03
Add Route Prompt
Add Not Diamond, choose
Route Prompt, map the question into Prompt and list the models it may choose from. Test it and read the label that comes back. - 04
Add the filter and the AI step
Click the plus icon, add Filter on the returned label, then add the AI app that answers. Pick a text rule: the label is text, and a wrong rule type never passes.
- 05
Publish
Click Publish to switch the Zap on. With four steps this is a multi-step Zap, so it needs a paid plan. A prompt that passes the filter costs two tasks, one that stops there costs one.
The Not Diamond action
Not Diamond gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Route Prompt
ActionIn Zapier“Sends the prompt to the /modelSelect endpoint which will return a label for which LLM should be called.”
Hands a prompt to Not Diamond and gets back the name of the model it recommends from your list, which later steps use to send the prompt to the right AI.
When a Not Diamond Zap breaks
Zapier ties no help article to Not Diamond and documents no app-specific limit. What breaks comes from how Zapier works in general, applied to a routing step.
Four cases cover most problems. If a Zap still stalls after these checks, the Zapier troubleshooting guide walks through the diagnosis.
Missing prompt or model list
Prompt and Models are both required. A trigger that brings an empty field, or a Zap with no models listed, stops at Route Prompt.Filter that never passes
Filter rules are typed. The label is text, so a number rule on it, or a typo in the model name you compare with, blocks every run.Old requests not processed
A Zap only reacts to what happens after it is switched on. Questions that came in before are never routed; handling them is a separate job.Flood after a bulk import
A trigger that suddenly returns a huge batch, after an import or a migration, can be held back by Zapier's flood protection.
Need help automating Not Diamond with Zapier?
A person reads every message.



