Skip to main content

Run a Make.com Workflow

Make.com is a powerful workflow automation platform for building multi-step tasks. ConsoleX can call Make.com workflows as tools so models can complete more complex workflows.

Basic flow​

  1. Create a workflow in Make.com that starts with a webhook trigger and ends with a webhook response.
  2. In ConsoleX, create a tool with interface type Make.com, then configure its description, webhook URL, and API key if required.
  3. Add the tool to a conversation so the model can call it autonomously.

Detailed steps​

Configure trigger and parameters in Make.com​

To let ConsoleX call a Make.com workflow, add a Webhook trigger module and generate a webhook URL. That URL becomes the tool function endpoint in ConsoleX.

Optional auth setup in Make.com​

To validate an auth token in Make.com, add a filter after the webhook trigger and use a condition similar to this:

{{get(map(4.`__IMTHEADERS__`; "value"; "name"; "authorization"); 1)}}

Configure the workflow response​

End the workflow with a Webhook Response module. The response body should be JSON and contain a data field. The object inside data becomes the tool result returned to the model.

Example:

{
  "status": "success",
  "data": {
    "attr": "value"
  }
}

Create the Make.com tool in ConsoleX​

When creating the tool:

  • Define a JSON Schema that matches the workflow input parameters.
  • Enable tool calling and choose GET or POST based on how the Make webhook receives parameters.
  • Set the interface type to Make.com.
  • Use the Make.com webhook URL as the tool endpoint.
  • If your workflow uses auth validation, paste the auth token into the tool’s API key field.

Choose the appropriate return handling mode, then save the tool.

Example workflow​

Here is a sample Make.com weather workflow you can download and import for reference:

Weather workflow

Notes​

  1. The tool JSON Schema must match the input parameters expected by the Make.com workflow, otherwise the model may not call it correctly. Use Make.com run history for debugging.
  2. A Make.com workflow must be published before it can be called repeatedly. Before publishing, you can still use one-off runs for debugging or to redetermine the data structure.