Make.com

Configure the Make.com Webhook Integration to let your Noem.AI chatbot trigger Make scenarios (flows) from natural-language instructions. The bot calls the configured webhook with a JSON payload you define and can use the scenario’s response inside the conversation.

What this action does #

• Sends an HTTP request (POST/GET) from the chatbot to a Make Custom Webhook or Public Endpoint.
  
• Passes structured data gathered from the conversation (Data Properties).
  
• Optionally returns data from Make (e.g., a ticket number, URL) for the bot to relay to the user.
  

Prerequisites #

• A Make.com account with a Scenario that starts with Webhook → Custom webhook (or an HTTP module that can receive requests).
  
• The scenario has been Saved and the Webhook URL is available.
  
• Any required credentials or keys used inside your Make scenario.
  

Creating the Make.com action #

1. Open Actions → Add → Make.com.
   The Make.com Webhook Integration form opens.
   
2. Name(required)
   A short, unique function name the bot will reference in its Instructions.
   
   • Example: make_create_support_ticket.
     
3. Description(required)
   Guidance that helps the AI know when to call this function and what information to collect.
   
   • Example:
     “Call make_create_support_ticket when the user reports a product issue or requests support. Collect: short title, detailed description, user email, product, severity.”
     
4. End Point(required)
   
   • Method: Choose POST (recommended) or GET.
     
   • URL: Paste the Make Custom Webhook URL (from the Webhooks module in your scenario).
     
   • Tip: Use the Hide Function Log in Chat toggle if you don’t want request logs rendered in the chat transcript.
     
5. Data Properties
   Define the fields the bot will include in the request body (for POST) or query string (for GET). Each property has:
   
   • Name: Machine-readable key (e.g., emailContent).
     
   • Type: String, Number, Boolean, Array, or Object.
     
   • Description: Clear instructions for the AI on what to capture.
     
   • Required: Check if the bot must obtain this value before calling the action.
     
6. Use Add New Property to define more fields.
   Use AI Assistance to generate property suggestions based on your Description.
   
7. Advanced Mode (optional)
   If enabled, you can configure headers (e.g., Authorization), query parameters, and response mapping rules.
   
8. Save
   Click Save to store the action.
   

Tip (testing endpoint): For initial testing, you can set End Point to a temporary URL from https://webhook.site/ to inspect the exact payload your bot sends.

Example configuration #

• Name: make_create_support_ticket
  
• Description:
  “Call when the user reports a bug or support issue. Ask for a concise title, detailed description, steps to reproduce, priority (low/medium/high), product area, and the user’s email if available. Confirm before sending.”
  
• End Point: POST https://hook.eu1.make.com/xxxxxxxxxxxxxxxxxxxxxxxx
  
• Data Properties:
  

Sample JSON payload (POST body):

{

  “title”: “Checkout 500 error”,

  “emailContent”: “Customer cannot complete payment. Steps: 1) Add item, 2) Click Pay, 3) 500 error. Expected: success. Actual: 500.”,

  “priority”: “high”,

  “productArea”: “Checkout”,

  “reporterEmail”: “[email protected]”,

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

Add rules to your bot’s Instructions #

Include explicit decision logic so the AI knows when and how to call the Make action, what to collect, and when to confirm.

Instruction snippet (example):

When the user reports a bug or requests technical support, call function `make_create_support_ticket`.

Before calling, collect:

– title (short)

– description (detailed, steps to reproduce)

– priority (low/medium/high)

– product area

– reporter email (use user.email if present; otherwise ask once)

Confirm the summary: “Create a support ticket with this info?” If yes, call the function.

If some fields are missing after one follow-up, proceed and mark missing fields as TBD.

Configuring the Make scenario #

1. In Make, create a Scenario with the Webhook → Custom webhook module and copy its URL.
   
2. Add downstream modules (e.g., create a ticket, send Slack notification, write to Google Sheet).
   
3. Parse JSON: The webhook module parses incoming JSON automatically; map fields (title, emailContent, etc.) to your modules.
   
4. Return data to the bot (optional):
   

Add an HTTP → Make a response module and return a JSON object such as:

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

• The bot can read ticketId/portalUrl and present them to the user.
  

Testing #

1. In Noem.AI preview chat, issue a command such as:
   “Report a bug: 500 error on Checkout after clicking Pay. Priority high.”
   
2. Verify the bot gathers missing details, asks for confirmation, then calls make_create_support_ticket.
   
3. In Make, run the scenario once to determine data structure and ensure modules map correctly.
   

Confirm the bot displays any returned values (e.g., “Ticket SUP-4821 created. Track it here: …”).