Zapier & Make.com Integration Guide
Automate AskVerdict debates with Zapier or Make.com. Connect to 5,000+ apps using triggers and actions via REST Hooks.
Connect AskVerdict to 5,000+ apps without writing code. Use Zapier or Make.com to automatically start debates from external triggers and route verdicts to any downstream tool.
Prerequisites
- An AskVerdict account with an API key (Developer Portal → API Keys)
- A Zapier or Make.com account (free tiers are sufficient for basic Zaps)
- Credits on your AskVerdict account — automated debates consume credits just like manual ones
Authentication
All Zapier and Make.com API calls authenticate using your AskVerdict API key.
Header: Authorization: Bearer vrd_your_api_key
You can validate your API key using the auth test endpoint — Zapier calls this automatically when you connect your account:
GET /api/zapier/auth/test
Authorization: Bearer vrd_your_api_key{
"id": "usr_abc123",
"email": "you@example.com",
"name": "Alice Johnson",
"plan": "byok"
}A 200 response confirms the key is valid.
Triggers
Triggers start a Zap when something happens in AskVerdict. AskVerdict uses the REST Hooks pattern: Zapier registers a webhook URL, and AskVerdict calls it when the event fires.
debate.completed
Fires when an AI debate finishes with a verdict.
Subscribe:
POST /api/zapier/triggers/debate-completed/subscribe
Authorization: Bearer vrd_your_api_key
Content-Type: application/json
{
"hookUrl": "https://hooks.zapier.com/hooks/catch/..."
}{
"id": "whk_abc123",
"hookUrl": "https://hooks.zapier.com/hooks/catch/..."
}Unsubscribe (called automatically by Zapier when you turn off or delete a Zap):
DELETE /api/zapier/triggers/debate-completed/subscribe
Authorization: Bearer vrd_your_api_key
Content-Type: application/json
{
"hookUrl": "https://hooks.zapier.com/hooks/catch/..."
}Sample payload (used by Zapier for field mapping during Zap setup):
GET /api/zapier/triggers/debate-completed/sample
Authorization: Bearer vrd_your_api_key[
{
"id": "dbt_sample_7f3a2b1c",
"question": "Should we expand into the European market in Q3?",
"status": "completed",
"mode": "balanced",
"verdict": {
"recommendation": "Proceed with phased European expansion, prioritising the DACH region.",
"confidence": 0.78,
"consensusReached": true,
"agentsUsed": ["claude-3-5-sonnet", "gpt-4o", "gemini-1.5-pro"],
"totalRounds": 3,
"pros": [
"DACH region shows 23% YoY growth in your target demographic",
"Regulatory alignment with existing UK operations reduces compliance overhead",
"Three competitors have pulled back, leaving a market gap"
],
"cons": [
"Upfront localisation cost estimated at $420k",
"Sales cycle typically 6–9 months longer in European B2B"
]
},
"cost": {
"totalUsd": 0.042,
"fundingSource": "user_credits"
},
"isPublic": false,
"createdAt": "2026-01-15T10:23:41.000Z",
"completedAt": "2026-01-15T10:24:18.000Z"
}
]Trigger Payload Fields
| Field | Type | Description |
|---|---|---|
id | string | Debate ID |
question | string | The debate question |
status | string | Always "completed" for this trigger |
mode | string | "balanced", "fast", or "thorough" |
verdict.recommendation | string | The AI verdict text |
verdict.confidence | number | Confidence score (0–1) |
verdict.consensusReached | boolean | Whether agents reached consensus |
verdict.agentsUsed | string[] | List of AI model identifiers |
verdict.totalRounds | number | Number of debate rounds |
verdict.pros | string[] | Supporting arguments |
verdict.cons | string[] | Counter-arguments |
cost.totalUsd | number | Estimated USD cost of the debate |
completedAt | string | ISO 8601 timestamp |
Actions
Actions let your Zap do something in AskVerdict — triggered by events in other apps.
create-debate
Starts a new debate in AskVerdict.
POST /api/zapier/actions/create-debate
Authorization: Bearer vrd_your_api_key
Content-Type: application/json
{
"question": "Should we adopt the new vendor proposal from TechCorp?",
"mode": "balanced"
}{
"id": "dbt_xyz789",
"question": "Should we adopt the new vendor proposal from TechCorp?",
"status": "running",
"mode": "balanced",
"createdAt": "2026-02-20T11:00:00.000Z"
}| Field | Required | Values | Default | Description |
|---|---|---|---|---|
question | Yes | String (10–2000 chars) | — | The question to debate |
mode | No | quick, balanced, deep | balanced | Debate mode (quick = fast, deep = thorough) |
Automated debates always use your credit balance — BYOK keys cannot be injected into Zapier workflows. Ensure your account has sufficient credits before setting up automated Zaps.
The debate runs asynchronously. The create-debate action returns immediately with status: "running". Use the debate.completed trigger in a separate Zap to capture the verdict.
Sample Zap Recipes
Recipe 1: New Debate Completed → Slack Notification
Route every completed verdict to a Slack channel for team visibility.
Trigger: AskVerdict — Debate Completed
Action: Slack — Send Channel Message
Message template:
*New AskVerdict Verdict*
*Question:* {{verdict_question}}
*Recommendation:* {{verdict_verdict_recommendation}}
*Confidence:* {{verdict_confidence_percent}}%
*Mode:* {{verdict_mode}}
<https://askverdict.ai/debates/{{verdict_id}}|View full debate>Setup steps:
- In Zapier, click Create Zap
- Trigger app: AskVerdict → Event: Debate Completed
- Connect your AskVerdict account (enter your API key)
- Test the trigger — Zapier fetches the sample payload
- Action app: Slack → Event: Send Channel Message
- Map the fields above using the data from Step 4
- Choose your target channel
- Turn the Zap on
Recipe 2: Completed Debate → Google Sheets Row
Log every verdict to a spreadsheet for trend analysis and reporting.
Trigger: AskVerdict — Debate Completed
Action: Google Sheets — Create Spreadsheet Row
Sheet columns:
| Column | AskVerdict Field |
|---|---|
| A — Date | completedAt |
| B — Question | question |
| C — Recommendation | verdict.recommendation |
| D — Confidence | verdict.confidence |
| E — Mode | mode |
| F — Consensus | verdict.consensusReached |
| G — Cost (USD) | cost.totalUsd |
| H — Link | https://askverdict.ai/debates/{{id}} |
Setup steps:
- Create a Google Sheet with the columns above (row 1 as headers)
- In Zapier, create a new Zap
- Trigger: AskVerdict → Debate Completed
- Action: Google Sheets → Create Spreadsheet Row
- Select your spreadsheet and sheet
- Map each column to the corresponding AskVerdict field
- Turn the Zap on
New debates will automatically append a row when they complete.
Recipe 3: Outcome Recorded → Email Summary
Send an email summary when a team member records an outcome on a debate, closing the feedback loop.
Trigger: AskVerdict — Debate Completed (filtered for debates with outcomes)
Filter: Only continue if verdict.consensusReached is true
Action: Gmail (or Email by Zapier) — Send Email
Email template:
Subject: Decision Outcome — {{question}}
Hi {{recipient_name}},
A decision has been finalised in AskVerdict.
Question: {{question}}
Verdict: {{verdict.recommendation}}
Confidence: {{verdict.confidence_percent}}%
Top arguments in favour:
{{verdict.pros_formatted}}
Key risks identified:
{{verdict.cons_formatted}}
View the full debate: https://askverdict.ai/debates/{{id}}
This summary was generated automatically by AskVerdict.Setup steps:
- In Zapier, create a new Zap
- Trigger: AskVerdict → Debate Completed
- Add a Filter step: only continue if
consensusReachedistrue - Action: Gmail → Send Email (or Email by Zapier → Send Outbound Email)
- Map the template fields to the AskVerdict trigger data
- Enter recipient email addresses (can be dynamic from earlier Zap steps)
- Turn the Zap on
Make.com (formerly Integromat)
Make.com supports the same REST Hooks pattern as Zapier. To set up an AskVerdict module in Make:
- Create a new Scenario in Make
- Add an HTTP → Watch for a Webhook module as the trigger
- Copy the generated webhook URL
- Manually call the subscribe endpoint from Make's HTTP module:
POST /api/zapier/triggers/debate-completed/subscribe
Authorization: Bearer vrd_your_api_key
{
"hookUrl": "https://hook.eu1.make.com/your-webhook-id"
}- Add your action modules (Google Sheets, Slack, Email, etc.)
- Map fields from the
debate.completedpayload using the field reference above
Make.com's native AskVerdict module is in development. Until it is available, use the HTTP module with the endpoints documented here. The REST Hooks pattern is fully compatible with Make's webhook modules.
Troubleshooting
| Issue | Solution |
|---|---|
| "Unknown trigger" error (404) | Only debate-completed is currently a supported trigger name |
| Zap not firing on debate completion | Confirm the Zap is turned on and the subscribe call succeeded (check for a 201 response with an id) |
create-debate returns DEBATE_CREATE_FAILED | Check your account's credit balance — insufficient credits will block debate creation |
| Question too short | The question field must be at least 10 characters |
| Auth test returns 401 | Your API key is invalid or has been revoked — generate a new one at Developer Portal → API Keys |
| Webhook not delivered | AskVerdict uses the same retry policy as standard webhooks — see the Webhooks guide for details |
Was this page helpful?