Grok Bot + n8n or Make: fixed workflows hand the judgment to a Bot
Keep predictable, step-by-step automations in n8n or Make, and send the steps that need judgment, like research or a reply draft, to a Grok Bot routine through its webhook.
Setup
- In Grok Bot, create a webhook-triggered routine. It gets a webhook URL and key, and the Bot receives the request body.
- In n8n, add an HTTP Request node where the workflow needs judgment; in Make, use an HTTP module. Send the record as JSON.
- Tell the routine where to put its result: a sheet row, a Notion page, a Slack message, or a draft for approval.
- Test with one record, then turn it on for new records only.
Starter prompt
This routine starts when [n8n / Make] sends a new [lead / order / ticket] as JSON.
1. Read the request body. If a required field is missing, post what's missing in [Slack channel] and stop.
2. [Judgment step: research the company / draft a reply / categorize the request].
3. Write the result to [sheet row / Notion database] with the record's ID, so the workflow can pick it up.
4. Anything that would go to a customer goes on a draft card for my approval.
Business fit
How this stack helps specific businesses:
- AgenciesAgencies with client automations in n8n or Make can add research and drafting without rebuilding them.
- Local & serviceA form-to-CRM workflow can hand each quote request to a Bot to draft the reply.
- Shopify & ecommerceOrder workflows can pass unusual orders to a Bot for a closer look.
- StartupsOps teams keep reliable plumbing in one tool and judgment calls in another.
Watch-outs
- We haven't seen this exact pairing published end to end. It's assembled from Grok Bot's webhook routines and the standard HTTP steps in n8n and Make, so test it first.
- Annika Helendi's experience with Lindy applies: complex, fixed pipelines stayed more reliable in Make than in an agent.
- Every webhook run uses Bot usage. Filter in n8n or Make so only records that need judgment reach the Bot.