Can Zapier Central handle conditional branching based on sentiment analysis from an OpenAI API call or should we build this directly in Make today?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Can Zapier Central handle conditional branching based on sentiment analysis from an OpenAI API call or should we build this directly in Make today?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
Zapier Central current availability product status 2026 conditional logic AI agents OpenAI integration Google ↗
Make.com OpenAI sentiment analysis router conditional branching documentation Google ↗
- Introducing Zapier Central · zapier.com
- Migrating from Agents to AI by Zapier · help.zapier.com
- Use conditional logic to filter and split your Zap workflows · help.zapier.com
- Make AI Toolkit + OpenAI Integration | Make · make.com
- If-else and Merge · help.make.com
- Router · help.make.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Zapier Central current availability product status 2026 conditional logic AI agents OpenAI integration OBSERVED | Google ↗ AI Mode ↗ | — | Other / navigational | — | — | 1x of 1 | |
Make.com OpenAI sentiment analysis router conditional branching documentation OBSERVED | Google ↗ AI Mode ↗ | — | Instruction | — | — | 1x of 1 |