Slack API ➔ Airtable Payload Specification

Technical reference for automating data exchange between Messaging and NoCode DB 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 Airtable intake pipeline and mapped to your NoCode DB targets.

Authentication & Event Specs

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

Sample Webhook JSON Payload

{
  "event": "message.channels_to_airtable",
  "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": "Airtable",
    "auth_mode": "Bearer Token",
    "target_endpoint": "https://api.airtable.com/v1/ingest",
    "mapped_fields": {
      "record_id": "{{source.channel_id}}",
      "base_id": "{{source.user_id}}",
      "table_name": "{{source.text}}",
      "fields": "{{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 Airtable 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.