Trigger Control

Manage incoming and outgoing webhooks — configure HTTP listeners that fire workflows from external events.

Overview

Trigger Control is the webhook management hub for TotalApp. Every webhook you create gets a unique URL that external systems (GitHub, Stripe, Shopify, Slack, or any service that supports webhooks) can call to start a workflow run automatically.

You can also configure outgoing webhooks — TotalApp posts a payload to an external URL when a workflow completes or when a specific node fires.

Coming Soon

Trigger Control is currently in development. The UI is visible in the Automation mode sidebar but is not yet fully functional. Webhook registration and delivery are planned for an upcoming release.

Planned Features

Incoming webhooks — unique HTTPS URLs per workflow; supports GET and POST; optional shared-secret HMAC verification.
Payload mapping — map JSON fields from the incoming payload to node input variables using a visual mapper.
Outgoing webhooks — POST a JSON payload to an external URL on workflow completion or node-level events.
Delivery log — per-webhook history of received and sent payloads with status codes and response bodies.
Retry policy — automatic retry with exponential back-off for failed outgoing deliveries.
Rate limiting — configure max calls per minute per webhook to protect against burst traffic.

Frequently Asked Questions

Is Trigger Control available to use right now?

Not yet. Trigger Control is currently in development — it appears in the Automation mode sidebar so you can see what's coming, but webhook registration and delivery are not yet functional. Existing workflow triggers (e.g. ecommerce webhooks, Linear, scheduled triggers) continue to work through their own dedicated integrations while Trigger Control is being built as the unified hub for all of them.

Will incoming webhooks require authentication?

Yes. The planned design gives each webhook a unique HTTPS URL and supports an optional shared-secret HMAC signature check, so you can verify that a payload genuinely came from the external service (GitHub, Stripe, Shopify, Slack, etc.) before it triggers a workflow run.

How will I map incoming JSON data to my workflow's nodes?

A visual payload mapper is planned, letting you point specific fields in the incoming JSON body at input variables on your workflow's nodes — no manual JSON-path scripting required. Until this ships, workflows that need external event data use the existing SSE-bridge trigger pattern with a matching node-side handler.

What happens if an outgoing webhook delivery fails?

Outgoing webhooks are planned to retry automatically using exponential back-off, and every attempt — success or failure — will be recorded in a per-webhook delivery log with status codes and response bodies, so you can diagnose failed deliveries without leaving TotalApp. Rate limiting will also be configurable to protect the target endpoint from burst traffic.