Mirror an Airtable table into Postgres — every page of it. Airtable returns 100 records at a time behind an offset token, so a single fetch silently truncates; this follows every page and unpacks the nested {id, fields} record shape, upserting on the Airtable record id so re-running is safe.
Append-only audit log and compliance reporting API. Record every significant action in your system — logins, data access, mutations, exports, config changes — search them flexibly, generate compliance summaries, and manage retention. No extra services needed: it's all Postgres.
A verified Discord Interactions (slash-command) endpoint. Checks Discord's Ed25519 request signature with verify_signature before doing any work, answers the PING handshake, logs interactions to Postgres and replies in-channel. Discord signs asymmetrically, so its public key must never be used as an HMAC secret.
Lightweight product analytics backend. Track any named event with arbitrary properties, then query counts and user histories. No third-party analytics service required — your data stays in your database.
Send Firebase Cloud Messaging (FCM) push notifications straight from your database — register device tokens, send to one device, or fan out to every device a user owns. No app server, no Firebase Admin SDK. A drop-in replacement for a Supabase + FCM setup.
Postgres-backed feature flag API. Create, toggle, and check flags from any service.
Two endpoints to satisfy GDPR Article 15 (right of access) and Article 17 (right to erasure). Every request is logged to an audit table. Data is kept on your own infrastructure — nothing leaves your database.
Query a GraphQL API with variables and store the result, with the error handling GraphQL actually needs: a failed query returns HTTP 200 with an errors array, so a status check alone silently stores nulls. Asserts on body.errors before writing, and keeps values in variables rather than interpolating into the query text.
Verify JWTs three ways - against a provider's JWKS (Auth0, Clerk, Cognito, Firebase), a static PEM public key, or an HS256 shared secret - then protect a real per-user Postgres resource scoped to the token's sub claim. Reference endpoints for every is_valid_jwt mode plus a working, owner-scoped notes API and a one-call multi:true migration.
Capture leads from any form, landing page, or webhook. Every submission is validated, stored in Postgres, and fires an instant Slack notification. Your data stays on your infrastructure.
Turn your Postgres data into secure MCP tools any AI client (Claude Desktop, Claude Code, Cursor) can call. Two-tier auth: one shared token for yourself, or per-user tenant-scoped tokens for your customers - minted via an HS256 exchange or verified directly against your OIDC provider's JWKS (Auth0, Clerk, Cognito). Every tool reuses the same in-config token checks as a normal Air Pipe route. Tool discovery (tools/list) is gated behind the same per-user token via list_authorizer, so unauthenticated clients cannot enumerate your tools or their input schemas (engine >= 1.7.0).
A production-shaped multi-tenant backend over Postgres: API-key authentication (sha256-hashed, generated server-side, revocable), strict per-tenant data isolation, plan-based limits, and usage metering. Every request resolves its API key to exactly one tenant and every query is scoped to it — cross-tenant access is structurally impossible.
The OAuth2 authorization-code flow with refresh, per user - the flow behind every 'connect your Google account' button. Single-use CSRF state, tokens sealed with AES-256-GCM (encrypt_value) and never stored in the clear, transparent refresh driven by an absolute expires_at, and correct handling of providers that send refresh_token only on the FIRST consent.
Deploy this config and three things appear immediately with zero extra work; Prometheus Metrics, Open Telemetry Tracing, OpenAPI Spec documentation. Every request becomes a trace you can inspect end-to-end: method, path, status code, latency, and which actions ran inside it. No annotations beyond the config. No code. No separate instrumentation setup.
Retrieval-Augmented Generation chatbot backed by Postgres + pgvector. Ingest your own documents, store OpenAI embeddings alongside them, and answer questions using only your data — no third-party vector DB, no proprietary cloud, nothing leaves your infrastructure. Includes seed, ingest, chat, history, and delete endpoints.
A production-shaped CRUD API over Postgres with three resource types (users, posts, comments) and optional JWT validation. No external services required — just a Postgres database. Deploy and start making requests in under 10 minutes.
Define a database connection and an auth check once, reference them everywhere. A Postgres starter that showcases Air Pipe reusable modules.
Private file storage on S3-compatible object storage where the file never transits Air Pipe. Postgres holds the metadata; clients upload straight to S3 via a presigned PUT and download via a short-lived presigned GET, so the bucket stays private and links expire. Works with AWS S3, Cloudflare R2, MinIO or Backblaze B2.
Receive Shopify order webhooks, verify the base64 X-Shopify-Hmac-Sha256 signature (is_valid_hmac with encoding: base64 — Shopify base64-encodes its digest where GitHub/Stripe/Slack use hex), and upsert orders into Postgres idempotently, with a recent-orders and paid-revenue reporting endpoint.
Approve/Reject buttons in Slack, end to end. Slack posts its interactivity payload as JSON inside a urlencoded `payload` FORM FIELD, so it must be parsed with yaml_to_json before anything can read it, and the signature is over the RAW body. Records the decision, then replaces the original message via response_url so the buttons disappear. Catches chat.postMessage failing as ok:false at HTTP 200, and a double-click is idempotent rather than an error.
Receives Stripe webhook events, verifies the signature, stores every event in Postgres with idempotency, and posts a Slack notification. One endpoint handles all event types.
A Twilio SMS bot served straight from your database. Receives inbound SMS via a Twilio webhook, replies instantly with TwiML, routes keyword commands to canned replies, handles STOP/START opt-out, and logs every message. No app server.
A zero-dependency webhook capture tool. Point any webhook sender at `/webhooks/log` and the full request — body, headers, and query params — is stored in your Postgres database. Replay stored events to your local dev server without re-triggering the original source. Useful for debugging Stripe, GitHub, Shopify, or any other webhook-based integration. Captures headers like `X-Stripe-Signature`, `X-GitHub-Event`, and `X-Hub-Signature-256` alongside the body so you have everything needed to replay or verify the original request.