Overview
Build event-driven integrations with inbound webhooks. Flows360 provides a unique, secure URL for your external systems to send real-time data. Whenever a system sends a JSON payload via an HTTP POST request to your webhook URL, it can trigger any workflow in your Flows360 account. This allows you to connect legacy systems, custom applications, or any service that supports webhooks, providing a universal entry point for your data integration and process automation needs. No polling required; get the data you need, the moment it's available.
Capability summary
Authentication
Authentication method: Webhook URL
Required scopes
] Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| payload | No | Yes | Represents the raw, unstructured JSON data received by the webhook. Write-only. |
| ACCOUNTS | Yes | Yes | |
| CONTACTS | Yes | Yes |
Supported actions
create_record
Create a new record in a target system using data from the incoming webhook payload.
pull_record
Retrieve an existing record's details. Often used within a workflow to check if a record exists before creating a new one.
Setup
- In your Flows360 account, create a new workflow and select "Inbound Webhook" as the trigger.
- Upon creation, Flows360 will generate a unique URL. Copy this URL.
- In your external application (the source system), navigate to the webhooks or API settings section.
- Paste the copied URL into the appropriate field for a new webhook endpoint.
- Configure the source system to send an HTTP POST request with a JSON payload to this URL when a specific event occurs (e.g., a new contact is created).
- Send a test request from the source system to the webhook URL.
- In the Flows360 workflow editor, use the received test payload to map the incoming JSON fields to the desired actions (e.g., creating a new record in another system).
- Activate your workflow. It will now run automatically each time the source system sends data to the webhook URL.
Limitations
- Payload Format: The endpoint only accepts JSON (
application/json) payloads. Other formats like XML or form-data will result in an error. - HTTP Method: Only HTTP POST requests are accepted. GET, PUT, PATCH, or DELETE requests will be rejected.
- Security: The generated webhook URL is unique and secure. However, it is a public endpoint. Anyone with the URL can send data to it. There is no additional authentication layer on the receiving end.
- Data Structure: The workflow must be configured to expect the specific JSON structure sent by the source application. Mismatches in the data structure may lead to workflow failures.
- Retries: The inbound webhook does not perform automatic retries for failed workflow executions. The source system is responsible for implementing its own retry logic if a request fails (e.g., due to a 5xx error).
Troubleshooting
My data isn't showing up in Flows360 after I sent it to the webhook URL. What should I do?
- Verify the URL: Ensure the webhook URL copied from Flows360 exactly matches the URL configured in the source system.n2. Check Source System Logs: Check the logs in your source application to confirm that it successfully sent the POST request and received a
200 OKor202 Acceptedresponse.n3. Inspect Payload Format: Confirm the source system is sending a valid JSON payload and that theContent-Typeheader is set toapplication/json.n4. Check Workflow Status: Ensure the corresponding workflow in Flows360 is active and published. Check the workflow's run history for any errors.
Can I send data in XML or form-data format?
No. The inbound webhook endpoint is designed to accept JSON payloads only. You must configure the source system to serialize data as JSON and set the Content-Type header to application/json.
How can I secure my webhook?
Treat the webhook URL as a confidential secret. Anyone who has the URL can send data to your workflow. If the sending system supports it, you can add a pre-shared secret or token in the request headers (e.g., Authorization: Bearer my-secret-token). Then, add a step in your workflow to verify this header value before processing the data.