Slack API ➔ Notion API Payload Specification

Technical reference for automating data exchange between Messaging and Workspace workflows.

💡 How this integration works:

1. Slack API triggers an event when message.channels occurs.
2. Data is packaged into a standard JSON webhook payload.
3. Payload is delivered into your Notion API intake pipeline and mapped to your Workspace targets.

Authentication & Event Specs

Parameter	Source (Slack API)	Destination (Notion API)
Auth Mechanism	`OAuth Bot Token`	`Bearer Integration Token`
Trigger Event	`message.channels`	`Ingest Pipeline`

Sample Webhook JSON Payload

{
  "event": "message.channels_to_notion",
  "timestamp": 1788105199,
  "source": {
    "platform": "Slack API",
    "auth_mode": "OAuth Bot Token",
    "data": {
      "channel_id": "sample_channel_id_val",
      "user_id": "sample_user_id_val",
      "text": "sample_text_val",
      "ts": "sample_ts_val"
    }
  },
  "destination": {
    "platform": "Notion API",
    "auth_mode": "Bearer Integration Token",
    "target_endpoint": "https://api.notion.com/v1/ingest",
    "mapped_fields": {
      "page_id": "{{source.channel_id}}",
      "database_id": "{{source.user_id}}",
      "last_edited_by": "{{source.text}}",
      "properties": "{{source.ts}}"
    }
  }
}

Quick Integration Setup

Retrieve your secret API credentials from your Slack API developer dashboard using authentication method OAuth Bot Token.
Configure the target endpoint URL to route payloads into the Notion API 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 `OAuth Bot Token` credentials.
`422 Unprocessable`	Schema Error	Check field keys alignment between source and target payload.