Pipe Studio

Tabs at a glance

• Event — sample payload and environment values your handler reads as context.env (not process.env).
• Design — graph view of triggers, HTTP steps, and code nodes for the pipe.
• Code — handler source and Monaco editing; aligns with the published bundle.
• Test — run Execute against the live published graph with a JSON body.
• Runs — recent executions for quick review.
• History — version list, diff context, and publish actions.

Publishing and runtime

Publish validates settings.pipe and bundles your handler. Only one enabled pipeline per endpoint is invoked for incoming webhooks; the runtime uses the current live version.

Tier limits apply to pipeline count, execution timeout, bundle size, and HTTP steps—see Pricing. Test Execute uses the same runtime as production with a synthetic event.

Library and official templates

In the Design tab, Library lists your code boxes and official provider templates. Templates load a starter pipe (often including a verify node) and handler source; applying one replaces the current graph and prefills declared environment keys in the Event tab.

Badges show whether the runtime verifies the provider cryptographically (Native verify), expects a callback token header (Token verify), or leaves verification to your filters and code (No native verify). Tier A marks providers with expanded onboarding in the repository docs (Stripe, GitHub, Slack, Shopify, Mercado Pago, Conekta, Flow).

API and CLI

Everything you do in the UI maps to REST endpoints for listing pipelines, creating versions, and executing tests. The official CLI runs build and push from your machine after you sign in with eventpipe login—the same session as the dashboard.