How to Connect Notion Maton to OpenClaw

Log in to your Maton account at maton.ai and create a new automation scenario. In Maton's scenario builder, add Notion as the integration target — you will be prompted to authorize Maton with your Notion workspace using OAuth. Once connected, define the Notion operations you want the scenario to perform: for example, 'Create Page in Database' with field mappings for title, description, tags, and status. Map the input fields using Maton's variable syntax — for example, `{{input.title}}` maps to the page title, and `{{input.tags}}` maps to a multi-select property. These variable names must match the JSON keys you will send from OpenClaw. After configuring the Notion steps, enable the 'Webhook Trigger' for the scenario. Maton will generate a unique webhook URL in the format `https://api.maton.ai/webhook/SCENARIO_ID`. Copy this URL — it becomes your MATON_WEBHOOK_URL in OpenClaw's config. Test the webhook manually from Maton's interface by clicking 'Test Trigger' and sending a sample payload. Verify that Notion receives the data correctly and creates the expected pages or updates the expected database records before connecting OpenClaw.

1# Sample Maton webhook payload structure
2# Send this JSON structure when calling your Maton webhook
3{
4  "title": "New task title",
5  "description": "Task details from OpenClaw",
6  "tags": ["openclaw", "automated"],
7  "status": "Incoming",
8  "source": "openclaw",
9  "created_at": "2026-03-30T10:00:00Z"
10}
11
12# Maton webhook URL format:
13# https://api.maton.ai/webhook/YOUR_SCENARIO_ID
14
15# Test your Maton webhook manually:
16curl -X POST "https://api.maton.ai/webhook/YOUR_SCENARIO_ID" \
17  -H "Content-Type: application/json" \
18  -d '{"title": "Test page", "description": "Manual test from curl", "status": "Incoming"}'

Open your OpenClaw config file at `~/.openclaw/config.yaml` and add the Maton integration under the `integrations` key. The `webhook_url` is the Maton scenario webhook URL from Step 1. The `notion_token` is your Notion internal integration token — find it at notion.so/my-integrations, create an integration if you do not have one, and copy the 'Internal Integration Token' (starts with `secret_`). The `notion_token` in OpenClaw's config is used for direct Notion read operations (fetching database schemas, reading pages) if you configure any. For Maton-triggered write operations, Maton uses its own Notion OAuth connection and does not require you to pass the token on each request. The `default_database_id` is optional but useful — it tells OpenClaw which Notion database to target by default when constructing payloads. Find the database ID from its Notion URL: `notion.so/YOUR_WORKSPACE/DATABASE_ID?v=VIEW_ID`. Run `clawhub reload` after saving the config to apply changes.

1# ~/.openclaw/config.yaml
2integrations:
3  notion-maton:
4    webhook_url: "https://api.maton.ai/webhook/YOUR_SCENARIO_ID"
5    notion_token: "secret_YOUR_NOTION_INTEGRATION_TOKEN"
6    default_database_id: "YOUR_NOTION_DATABASE_ID"  # optional
7    timeout: 15              # seconds to wait for Maton response (default: 10)
8    retry_on_failure: true   # retry once if Maton returns 5xx (default: false)
9    payload_template:        # default fields added to every webhook call
10      source: "openclaw"
11      environment: "production"

Test the full pipeline from OpenClaw to Maton to Notion. From your terminal or OpenClaw's config, trigger the Maton webhook with a test payload that matches your scenario's input variable schema. Verify that Maton receives the payload (check Maton's execution logs in your dashboard), processes the Notion steps, and creates or updates the expected Notion records. If you are using OpenClaw's HTTP integration features to call the webhook, the test below shows the curl-equivalent pattern that OpenClaw will execute. This is useful for debugging — if curl works but OpenClaw does not trigger correctly, the issue is in your OpenClaw workflow configuration, not the Maton/Notion connection. Check Maton's execution history after each test — Maton shows you exactly which steps ran, what data was passed to Notion, and any errors that occurred. This is significantly easier to debug than raw Notion API calls because each step is logged individually.

1# Test the full pipeline: OpenClaw → Maton → Notion
2curl -X POST "https://api.maton.ai/webhook/YOUR_SCENARIO_ID" \
3  -H "Content-Type: application/json" \
4  -H "X-Maton-Auth: YOUR_MATON_AUTH_TOKEN" \
5  -d '{
6    "title": "OpenClaw Integration Test",
7    "description": "Testing OpenClaw to Maton to Notion pipeline",
8    "tags": ["test", "openclaw"],
9    "status": "In Progress",
10    "source": "openclaw"
11  }'
12
13# Expected Maton response:
14# {"success": true, "execution_id": "exec_abc123", "status": "completed"}
15
16# Check Maton execution logs:
17# maton.ai/dashboard → Automations → YOUR_SCENARIO → Execution History

With the connection verified, configure an OpenClaw workflow that automatically triggers the Maton webhook based on events or chat commands. The workflow pattern is: define a trigger (chat keyword, scheduled time, or external event), map the relevant data to the Maton payload schema, and call the webhook. The example config below shows a keyword-triggered workflow: when a user types a message starting with 'log:' in OpenClaw chat, the workflow extracts the content after 'log:', builds a Maton payload, and sends it to the webhook. Maton then creates a Notion log entry with that content. For RapidDev teams working with complex Notion setups — multiple databases, cross-linked pages, approval chains — Maton scenarios can be designed to handle all the Notion complexity while OpenClaw just sends clean, simple payloads. RapidDev's integration guides include templates for common Notion automation patterns that work with Maton out of the box. Test the workflow by running OpenClaw and entering a trigger message. Watch Maton's execution dashboard to confirm the automation fires and Notion receives the update.

1# ~/.openclaw/config.yaml — keyword-triggered Maton/Notion workflow
2workflows:
3  notion-log:
4    trigger:
5      type: chat-message
6      pattern: "^log: (.+)"   # matches 'log: [any content]'
7    actions:
8      - type: http-post
9        integration: notion-maton
10        payload:
11          title: "Log Entry — {{trigger.timestamp_date}}"
12          description: "{{trigger.match.1}}"   # captured text after 'log: '
13          tags: ["log", "openclaw"]
14          status: "Done"
15          source: "openclaw-chat"
16          created_at: "{{trigger.timestamp_iso}}"
17
18  notion-research-log:
19    trigger:
20      type: task-complete
21      task_type: web-search
22    actions:
23      - type: http-post
24        integration: notion-maton
25        payload:
26          title: "Research: {{trigger.query}}"
27          description: "{{trigger.summary}}"
28          tags: ["research"]
29          status: "Archived"
30          source: "openclaw-research"