Send a record’s data to another app (webhook)
The Send to another app step sends the record’s data, or a body you design, to an outside app’s URL, digitally signed, and retries on temporary failures.
Before you start · for owners and managersThe permission to edit workflows
- You need: The permission to edit workflows
Steps
{{name}}.How it works
Internal and private URLs are refused. The action accepts only public addresses on the internet.
Every request carries a signature made with the automation’s own secret. The secret isn’t shown in Corteksa.
Sending is “at least once”: after a timeout or a temporary error, it’s resent with the same body and the same idempotency key, so the app ignores the duplicate.
The new record data format (version 2) sends options by their names and files as signed links. Old steps stay on version 1 until you change them.
The run log keeps only the domain name, not the full URL.
Signature and header details for developers are in Subscribe to Webhooks to receive record changes.
If something goes wrong
A real example
The accounting system needs every signed contract.
- A field changes: the stage changes to “Signed”.
- Send to another app with a custom body: the contract number, the value and the client.
The invoice shows up in accounting without anyone typing it in.