n8n

Use the n8n Webhook Integration to let your Noem.AI chatbot trigger n8n workflows from natural-language instructions. The bot will call an n8n webhook with a structured JSON payload and can relay the workflow’s response back to the user.

What this action does #

• Sends an HTTP request (POST/GET) from the bot to an n8n Webhook (self-hosted or Cloud).
  
• Includes Data Properties extracted from the conversation.
  
• Optionally displays values returned by n8n (e.g., ticket IDs, URLs) in the chat.
  

Prerequisites #

• An n8n Workflow that starts with the Webhook node (or an HTTP endpoint that can receive requests).
  
• The workflow is Activated, and the Production Webhook URL is available.
  
• Any credentials used by downstream nodes (e.g., Slack, CRM) are configured in n8n.
  

Create the n8n action #

1. Open: Actions → Add → n8n to open n8n Webhook Integration.
   
2. Name (required)
   The function name you’ll reference in your bot’s Instructions.
   Example: n8n_create_support_ticket.
   
3. Description (required)
   Explain when this action should be called and what the bot must collect.
   Example:
   “Use n8n_create_support_ticket when the user reports a product issue. Gather title, detailed description, priority, product area, and reporter email. Confirm before sending.”
   
4. End Point(required)
   
   • Method: POST (recommended) or GET.
     
   • URL: Paste your n8n Webhook URL (production URL if your workflow is active).
     
   • (Optional) Hide Function Log in Chat to suppress request logs in the transcript.
     
5. Data Properties
   Define the JSON fields sent to n8n. For each property set:
   
   • Name (e.g., emailContent, priority)
     
   • Type (String, Number, Boolean, Array, Object)
     
   • Description (clear guidance for the AI on what to capture)
     
   • Required (must be present before the call)
     
6. Use Add New Property to add fields. AI Assistance can suggest properties from your Description.
   
7. Advanced Mode (optional)
   Configure custom headers (e.g., Authorization), query params, and response mapping rules if your webhook expects them.
   
8. Save
   Click Save to store the action.
   

Tip (payload inspection): During setup, you can temporarily use https://webhook.site/ as the End Point to see the exact payload the bot sends.

Example configuration #

• Name: n8n_create_support_ticket
  
• Description:
  “Call when a user reports a bug or asks for support. Collect: short title, detailed description with steps to reproduce, priority (low/medium/high), product area, reporter email (use user.email if available). Confirm before sending.”
  
• End Point: POST https://n8n.example.com/webhook/abcd1234…
  
• Data Properties:
  

Sample JSON (POST body):

{

  “title”: “Checkout 500 error”,

  “emailContent”: “Steps: 1) Add item 2) Click Pay → 500. Expected: success. Actual: 500.”,

  “priority”: “high”,

  “productArea”: “Checkout”,

  “reporterEmail”: “[email protected]”,

  “attachments”: [“https://files.noem.ai/f/abc123.png”]

}

Returning data to the bot (optional):
Add an HTTP Response node in n8n and return JSON such as:

{ “status”: “created”, “ticketId”: “SUP-4821”, “portalUrl”: “https://support.example.com/tickets/SUP-4821” }

The bot can present these values to the user.

Add decision rules in your bot’s Instructions #

Use explicit, testable rules so the AI knows when to call this function, what to collect, and when to confirm.

Instruction snippet:

When a user reports a bug or requests support, call function `n8n_create_support_ticket`.

Collect: title, detailed description (steps to reproduce), priority, product area, reporter email (use user.email if available).

Confirm the summary with the user (“Create this support ticket now?”). If confirmed, call the function.

If a required field is missing after one follow-up, proceed and mark it as TBD.

Testing #

1. Activate the n8n workflow and copy the Production Webhook URL.
   
2. In Noem.AI preview chat, say:
   “Create a support ticket: Checkout throws 500 after Pay. Priority high.”
   
3. Ensure the bot gathers any missing fields, confirms, then calls n8n_create_support_ticket.
   
4. In n8n, check the Executions list to verify the payload and downstream actions.
   

If you returned data, confirm the bot displays it (e.g., “Ticket SUP-4821 created. Track it here: …”).