Zapier and Make
Use a standard HTTP POST action to call the EchoStack Evaluation API from Zapier, Make, or any automation platform.
Outcome
Every new form submission, CRM record, or webhook payload is evaluated before your team acts — routed by status and next_action.
Prerequisites
- Eval API quickstart completed
- Live deployment and
ech_dw_…secret
Architecture
Trigger (new form / webhook / CRM row)
→ HTTP POST /v1/evaluate
→ Filter or paths on JSON.status
→ QUALIFIED → Slack / CRM update
→ PARTIAL → email sequence
→ FAILED → close loop
Request
| Setting | Value |
|---|---|
| Method | POST |
| URL | https://api.getechostack.com/v1/evaluate |
| Header | Authorization: Bearer ech_dw_<secret> |
| Header | Content-Type: application/json |
Body (transcript)
{
"input_type": "transcript",
"input": [
{
"role": "user",
"content": "We're a 50-person SaaS team. Budget approved for Q2."
}
],
"options": { "request_next_action": true }
}
Body (form fields as transcript)
Map flat form fields into a single user message:
{
"input_type": "transcript",
"input": [
{
"role": "user",
"content": "Form submission:\n- company: Acme Inc\n- role: VP Sales\n- budget: $50k\n- timeline: Q2"
}
],
"options": { "request_next_action": true }
}
Or use input_type: "form" when your playbook expects structured form input — see the API reference.
Zapier setup
- Trigger: e.g. New Form Response, Webhook Catch Hook, New CRM Contact.
- Action: Webhooks by Zapier → POST.
- Paste URL, headers, and JSON body above; map dynamic fields from the trigger step.
- Filter / Paths: use
statusfrom the response (Zapier parses JSON automatically).- Path A:
statusequalsQUALIFIED - Path B:
statusequalsPARTIAL - Path C:
statusequalsFAILEDorESCALATE
- Path A:
Make setup
- HTTP → Make a request module.
- Configure method, URL, headers, and body as above.
- Add a Router on
statusfrom the HTTP module output.
Branching reference
| status | Typical automation |
|---|---|
| QUALIFIED | Create deal, notify Slack, book Calendly |
| PARTIAL | Add to nurture, send missing-field email |
| FAILED | Tag disqualified, no rep assignment |
| ESCALATE | Page on-call or route to senior rep |
Use next_action for finer steps (BOOK_MEETING, GATHER_INFO, NURTURE, etc.).
Verify
Run the scenario once, then check Recent evaluations on your deployment page in the dashboard.
Troubleshooting
| Issue | Fix |
|---|---|
Empty or wrong status |
Confirm JSON body; deployment must be live. |
| 401 | Secret must include ech_dw_ prefix in Bearer token. |
| Timeout | Evaluation is synchronous; allow ≥30s on HTTP modules. |
Related
- n8n integration (official community node)
- Eval API quickstart