This guide walks you through setting up a Call a webhook step in your Corma workflow. Use this action to send an HTTP request to an external URL — for example, to notify another system, trigger an integration, or push data out of Corma when a workflow runs.
Add the step
From your workflow builder, add a new step and select Call a webhook from the list of available actions. This action sends an HTTP request to an external URL and can optionally read the response back into your workflow.
Name your step
By default, the step is named something like step6. You can rename it using the pencil icon next to the Step name field.
Tip: Later steps in your workflow can reference this step's output using the format step6.field (substituting your actual step name). Choose a clear, descriptive name if you plan to reuse its output further down the workflow.
Choose the HTTP method
Under Method, select the HTTP verb for your request:
GET — retrieve data from the external URL POST — send data to create something PUT / PATCH — update an existing resource DELETE — remove a resource
Pick the method required by the external API or service you're calling. This field is required (marked with a red asterisk).
Enter the URL
In the URL field, enter the full endpoint you want to call, e.g.: https://api.example.com/webhook
This field is required. You can also use dynamic values from earlier steps in your workflow by referencing them here (indicated by the { } icon next to the field).
Add headers (optional but common)
Use the Headers section to pass any HTTP headers your endpoint expects. A common example is:
HeaderValueContent-Typeapplication/json
To add a header:
Enter the header name in the left field and its value in the right field. Click + Add to add additional header rows. Use the trash icon to remove a header row you no longer need.
Like the URL field, header values can also reference dynamic data from earlier in the workflow using { }.
Decide whether to read the response
Toggle Read response on if you want Corma to capture the webhook's response and make it available to later steps (e.g., step6.field). Leave it off if you only need to fire the request without using anything back from it.
Save and test
Once everything is configured, save the step and run a test of your workflow to confirm the webhook fires correctly and — if enabled — that the response is captured as expected.
