Skip to content

Developer platform

Built for developers when no-code isn't enough.

Publish events from your application, receive signed webhooks, track website activity without cookies, and turn any API into a connector.

Available

REST API

Everything the dashboard does for automations is available over REST.

  • API keys with scopes for workflows, executions, connections, events and hooks
  • A request ID on every response, to quote in support requests
  • Custom events (custom.…) that start workflows, published once per idempotency key
  • Endpoints for workflows, executions (replay, cancel), connections, hooks and packs
Publish a custom event
curl -X POST https://plugflow.in/v1/workspaces/current/events \
  -H "Authorization: Bearer pf_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "custom.lead.created",
    "payload": {
      "email": "[email protected]",
      "source": "pricing-page"
    },
    "idempotencyKey": "lead-8812"
  }'

# 202 Accepted
# { "eventId": "…", "executionIds": ["…"] }
Available

Reliable inbound events

Each inbound hook has its own URL, secret and authentication mode. Custom events can also be sent over the API.

  • HMAC signature, header secret or URL authentication
  • Replay protection: a timestamp window, and each signature accepted once
  • Secret rotation
  • Rate limiting per hook
  • Native modes for Razorpay and Stripe signatures
HMAC-signed delivery
x-plugflow-signature: t=<unix seconds>,v1=<hex hmac_sha256(secret, "<t>.<raw body>")>

# The timestamp must be within 5 minutes.
# Each signature is accepted once.
# 202 { "ok": true, "eventId": "…", "executions": 1, "requestId": "…" }
Available

Website events

One script tag turns form submissions and clicks into events that workflows can react to.

  • Publishable site keys, safe to ship in a page
  • Keys work only on the domains you approve
  • Cookie-free: no cookies are set in the browser
  • Served from /sdk.js
Website snippet
<script src="https://plugflow.in/sdk.js" data-key="pk_…" async></script>

<!-- a form becomes a web.lead.created event -->
<form data-plugflow-event="lead.created" data-plugflow-source="pricing">
  …
</form>

SDKs

SDKs ready — public registry distribution coming soon

The SDKs are built and tested in the PlugFlow repository. They are not on npm, Packagist or PyPI yet, so there is no install command to give you today. Until they are published, use the REST API directly.

  • npm publishing pending

    Node

    TypeScript client and webhook signature helpers.

  • Packagist publishing pending

    PHP

    PHP 8.1+ client with a Laravel service provider and facade.

  • PyPI publishing pending

    Python

    Python 3.9+ client on the standard library.

Custom connectors

Describe any API once. Use it in every workflow.

A connector is a manifest: authentication, actions, and how responses map to outputs. Keep it private to your workspace, or submit it for review to share it as a community connector.

  1. 1Manifest
  2. 2Test
  3. 3Enable
  4. 4Submit
  5. 5Platform review
  6. 6Community connector

Connector SDK

Define a connector in TypeScript and run its actions and health check locally, with secrets masked in the output.

Command-line tool

Scaffold, validate, run, health-check and submit a manifest from your terminal.

Community review

Submitted connectors are reviewed by PlugFlow before anyone else can enable them.

Connect. Automate. Flow.

Send your first custom event.

Create a workspace, make an API key under Settings → API keys, and publish an event that starts a workflow.

Developers — REST API, webhook automation, SDKs and custom connectors · PlugFlow