Skip to main content
Dilli automations let you catch inbound webhooks, validate the payload, and respond or call other services without managing servers.

How it works

  • Trigger: Each automation has a unique URL. Point external tools (payments, forms, shipping, etc.) at it.
  • Validate: Define simple rules so bad payloads are stopped before actions run.
  • Act: Chain outgoing HTTP calls, branch on conditions, and shape the final response you want to return.
  • Respond: Send back a clean HTTP reply (status, headers, body) to the caller.

Pause and resume

  • Pause an automation to stop processing temporarily (helpful during maintenance or testing).
  • While paused, new requests get a “temporarily unavailable” response and no actions run.
  • Resume to pick up normal processing instantly.

Inbox and replay

  • Every request is logged in an Inbox with method, path, body, timestamps, and whether it succeeded.
  • Replay any past request to test changes without waiting for a live event.
  • Logs stay for 30 days by default (plan-dependent retention options may apply).

Common uses

  • Catch payment or subscription webhooks and sync them to CRM records.
  • Power dynamic redirects after form submissions (e.g., route to different thank-you pages).
  • Enrich incoming data with a quick call to a third-party API, then return a tailored response.

Redirection

If defined, the flow will redirect the request to a specific URL after all actions are executed.

Response

Define the structure of the automation response, including HTTP status, headers, and body.