Airtable ➔ Stripe Payload Specification

Technical reference for automating data exchange between NoCode DB and Payments workflows.

💡 How this integration works:

1. Airtable triggers an event when record.created occurs.
2. Data is packaged into a standard JSON webhook payload.
3. Payload is delivered into your Stripe intake pipeline and mapped to your Payments targets.

Authentication & Event Specs

Parameter	Source (Airtable)	Destination (Stripe)
Auth Mechanism	`Bearer Token`	`Bearer Secret Key`
Trigger Event	`record.created`	`Ingest Pipeline`

Sample Webhook JSON Payload

{
  "event": "record.created_to_stripe",
  "timestamp": 1788105198,
  "source": {
    "platform": "Airtable",
    "auth_mode": "Bearer Token",
    "data": {
      "record_id": "sample_record_id_val",
      "base_id": "sample_base_id_val",
      "table_name": "sample_table_name_val",
      "fields": "sample_fields_val"
    }
  },
  "destination": {
    "platform": "Stripe",
    "auth_mode": "Bearer Secret Key",
    "target_endpoint": "https://api.stripe.com/v1/ingest",
    "mapped_fields": {
      "session_id": "{{source.record_id}}",
      "customer_email": "{{source.base_id}}",
      "amount_total": "{{source.table_name}}",
      "currency": "{{source.fields}}"
    }
  }
}

Quick Integration Setup

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