Skip to content
SETU by SUPREME AI
Beta

Webhooks and triggers

Get app events, finished runs, approvals and spend alerts sent to your server, with replay for failed deliveries.

How it works

  1. 1

    Add your endpoint

    Set the webhook URL for your project in the console.

  2. 2

    Subscribe

    Ask for an app event, such as a new email, for one of your users.

  3. 3

    Verify and handle

    Check the signature, then act on the event. Failed deliveries can be replayed.

Try it

Replace $SETU_API_KEY with a key from the Setu console.

Subscribe and verify

# Send a webhook when customer_42 gets a new email.
curl https://setu.supremeai.services/api/setu/v1/trigger-subscriptions \
  -H "Authorization: Bearer $SETU_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "trigger": "GMAIL_NEW_EMAIL", "userId": "customer_42" }'

What it does

  • Trigger subscriptions per end user.
  • Webhooks for runs, approvals, spend thresholds and connection health.
  • Replay of failed deliveries.
  • Start a workflow when a new email arrives.
  • Tell your user when an approval is waiting.
  • Alert your team when spend reaches a threshold.

Limits and status

Beta
  • Needs the triggers:write scope and an environment-bound key.
  • The user must have connected the app the trigger watches.
  • Not yet: A large catalog of app triggers. Only a few are defined.

Status last checked 2026-10-21.

Questions

Which events are sent?

Approvals (requested, approved, denied), executions (succeeded, failed), connections (connected, failed, revoked, attention required), spend thresholds and trigger events.

Which triggers exist?

A small set today: new Gmail email, new GitHub issue or pull request, Slack message, Stripe payments, a schedule, and a generic inbound webhook.

Start building with Setu

No Setu fee during beta. Create a key and make your first call.