The offer record connects the stack
Use Offers to define the product, price, checkout mode, invoice, and automation context before Custom API and Drip receive events.
Integration pair
Custom API + Drip
Use Custom API and Drip together with Plandalf as the layer that ties checkout, payments, invoices, integrations, and lifecycle automation together.
Common setup
Most teams use Custom API as their sdk layer and Drip as their email layer, with Plandalf in the middle handling the checkout, Offers, invoices, integrations, and the events that fire after a purchase.
See Custom API and Drip docs for connection details.
Product surfaces behind this integration
This legacy integration URL now points builders toward the same product reality as the canonical app-pair guide: Offers, payment options, invoices, integrations, Automations, API docs, and webhooks.
Purchase automation carries the details
Automations and webhooks let Custom API and Drip receive buyer, product, payment, invoice, coupon, and deadline context.
Integration settings remain visible
Confirm Stripe, PayPal, TaxJar, Avalara, and test-mode routing before sending the Custom API and Drip path live.
Use the richer guide from here
Keep moving from this page into canonical integration docs, platform pages, stack guides, and sequence recipes so every Custom API or Drip mention has a useful next step.
Open canonical app-pair guide Use the richer Custom API and Drip implementation guide. Custom API platform page Roles, capabilities, and setup notes for Custom API. Drip platform page Roles, capabilities, and setup notes for Drip. API-first stack SDK checkout, API keys, webhooks, payment processors, and invoices.