This article explains how to use the Catch webhook Info trigger to start a workflow from an external tool, and the Make HTTP Request action to send data from a workflow to an external tool.
Applicable Plans: Available on all plans.
Prerequisites
- You have a workflow already created. See how to build your first workflow if you have not created one yet.
- To receive data, you have the ability to send an HTTP POST request from the external tool — most platforms call this a webhook or a custom integration.
- To send data, you have the destination URL for the external tool's API endpoint, and any authentication details it requires.
Receiving data from an external tool
Use the Catch webhook Info trigger to start a workflow whenever an external tool sends data to a unique URL.
-
In the trigger picker, select Inbuilt Triggers, then choose Catch webhook Info from the list.
-
On the Webhook Data tab, click Copy to copy the webhook URL generated for this workflow.
Note: The field displays a shortened version of the URL. Copy always copies the full, unique URL.
-
In the external tool, configure it to send an HTTP POST request containing the payload to the copied URL.
Note: The payload must be valid JSON. HappyFox Workflows cannot parse other formats, such as XML or form-encoded data.
-
Trigger a test event from the external tool so it sends a payload to the URL.
-
If the panel still shows No Webhook Received, click Try Again to check for new data.
-
Select the received payload from the list under Last refreshed [time] — for example, Webhook #1.
-
Review the fields extracted from the payload — these become available as dynamic values in later workflow steps — then click Continue to complete the trigger setup.
Note: Reopening the Catch webhook Info trigger to review or change its data does not change the webhook URL. You can revisit the trigger and select a different received payload at any point without needing to update the external tool's configuration.
Sending data to an external tool
Use the Make HTTP Request action to send data from a workflow to any external tool's API endpoint.
Note: Make HTTP Request sends an HTTP request only — it does not validate what the destination endpoint does with that request. Configure the URL, method, and body carefully, and confirm the expected behavior with the owner of the external system before enabling a workflow that uses methods such as PATCH or DELETE, which can modify or remove data.
-
In your workflow, click Add Action to open the action picker.
-
Search for and select Make HTTP Request under Inbuilt Actions.
-
In the URL field, select or enter the destination URL. Click Insert Merge Fields to use a dynamic value from an earlier step instead of a fixed URL.
-
Select the HTTP Method — GET, POST, PATCH, PUT, or DELETE.
-
Enter any required Headers in JSON format, for example:
{"Content-Type": "application/json"}.Note: Make HTTP Request has no separate authentication field. Include any required API key or bearer token as a header.
-
Optionally, enter a Request Body in JSON format, for example:
{"name": "John Doe", "age": 28}. -
Click Run Test or Save & Test to send the request and confirm the external tool responds as expected.
Note: The response returned by the external tool is captured and available for use in later workflow steps. If the request fails — for example, a timeout or a non-2xx response — the error is shown in Run History.
-
Click Save to finish configuring the action.
Your workflow can now receive data from an external tool using Catch webhook Info, and send data to one using Make HTTP Request. Next, use Run History to confirm each request succeeded and review the response returned by the external tool.