HubSpot form → evaluate → route
Qualify inbound HubSpot form submissions with EchoStack before updating deal stage, assigning owners, or starting nurture.
Outcome
Partial submissions stay in nurture; strong fits create or update CRM records and notify sales while the lead is still hot.
Prerequisites
- Eval API quickstart with a lead qualification playbook (e.g. BANT)
- HubSpot form or workflow trigger
- n8n, Zapier, Make, or a small backend to call the API
Architecture
HubSpot new form submission
→ Automation (n8n / Zapier / workflow webhook)
→ POST /v1/evaluate (form content as input)
→ Branch on status
→ QUALIFIED → create/update deal, assign rep
→ PARTIAL → enrollment in nurture workflow
→ FAILED → tag disqualified, no owner assignment
Map form fields to input
EchoStack does not read HubSpot directly in the eval-only product — your automation passes submission fields into input.
Example (partial submission — missing budget and timeline):
{
"input_type": "transcript",
"input": [
{
"role": "user",
"content": "Form submission:\n- company: Startup Co\n- role: Sales Manager\n- problem: Manual data entry slows our team\n- budget: Not specified\n- timeline: Not specified"
}
],
"options": { "request_next_action": true }
}
Expected result: status may be PARTIAL with missing_fields listing gaps — route to a nurture sequence instead of assigning a rep.
Example (strong fit):
{
"input_type": "transcript",
"input": [
{
"role": "user",
"content": "Form submission:\n- company: Acme Corp\n- role: VP Revenue\n- budget: $80k approved\n- timeline: Live by end of Q2\n- team_size: 120"
}
],
"options": { "request_next_action": true }
}
Expected: QUALIFIED with next_action such as BOOK_MEETING — update HubSpot deal stage and notify Slack.
n8n (recommended)
- Trigger: HubSpot → New Form Submission (or webhook from HubSpot workflow).
- EchoStack → Evaluate with Form Fields or a formatted transcript string.
- Switch on
{{ $json.status }}. - HubSpot nodes on each branch: update contact, set lifecycle stage, create task.
See n8n integration for credential and workflow import steps.
Zapier / Make
Use the Zapier & Make HTTP POST pattern with HubSpot as the trigger app.
Verify
- Submit a test form (or use sample JSON above in Test evaluation).
- Confirm Recent evaluations shows the expected
status. - Confirm HubSpot only updates on the branch you expect.
Troubleshooting
| Issue | Fix |
|---|---|
| Always PARTIAL | Include all fields your playbook manifest requires in the transcript text. |
| HubSpot not updating | Check automation branch filters match exact status strings. |
| Duplicate evaluations | Debounce in n8n (e.g. only run on first submission ID). |