Make.com ➔ Supabase Payload Specification

Technical reference for automating data exchange between Automation and Backend/DB workflows.

💡 How this integration works:

1. Make.com triggers an event when scenario.triggered occurs.
2. Data is packaged into a standard JSON webhook payload.
3. Payload is delivered into your Supabase intake pipeline and mapped to your Backend/DB targets.

Authentication & Event Specs

Parameter	Source (Make.com)	Destination (Supabase)
Auth Mechanism	`API Key Header`	`Anon / Service Role Key`
Trigger Event	`scenario.triggered`	`Ingest Pipeline`

Sample Webhook JSON Payload

{
  "event": "scenario.triggered_to_supabase",
  "timestamp": 1788105197,
  "source": {
    "platform": "Make.com",
    "auth_mode": "API Key Header",
    "data": {
      "execution_id": "sample_execution_id_val",
      "scenario_id": "sample_scenario_id_val",
      "status": "sample_status_val",
      "data_output": "sample_data_output_val"
    }
  },
  "destination": {
    "platform": "Supabase",
    "auth_mode": "Anon / Service Role Key",
    "target_endpoint": "https://api.supabase.com/v1/ingest",
    "mapped_fields": {
      "schema": "{{source.execution_id}}",
      "table": "{{source.scenario_id}}",
      "commit_timestamp": "{{source.status}}",
      "record_data": "{{source.data_output}}"
    }
  }
}

Quick Integration Setup

Retrieve your secret API credentials from your Make.com developer dashboard using authentication method API Key Header.
Configure the target endpoint URL to route payloads into the Supabase intake pipeline.
Map incoming schema properties according to the JSON specification detailed above.

Expected HTTP Response Codes

Status Code	Meaning	Troubleshooting Step
`200 OK`	Success	Payload accepted and queued for routing.
`401 Unauthorized`	Auth Failure	Verify headers for valid `API Key Header` credentials.
`422 Unprocessable`	Schema Error	Check field keys alignment between source and target payload.