Connect any application with a custom webhook
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.
Common use cases
- Real-time event-driven automation
- Connecting to services without native APIs
- Receiving data from IoT devices
- Integrating with custom-built applications
- Triggering workflows from third-party notifications
- Capturing leads from marketing forms
Sync scenarios
- New customer notifications
- Order status updates
- Form submissions
- IoT device signals
- System alerts and events
- Payment confirmations
Objects supported
- ACCOUNTS
- CONTACTS
- payload
Actions
- pull_record
- create_record
Frequently asked questions
What is an inbound webhook?
An inbound webhook provides a unique URL that allows external systems to send data to your Flows360 account in real time via an HTTP POST request.
What format does the data need to be in?
The inbound webhook is designed to receive JSON payloads, which is the standard format for most modern web services.
How does this trigger a workflow?
When data is successfully posted to your unique webhook URL, it acts as a trigger event, initiating the associated workflow and making the payload data available for subsequent steps.
Can I use this to connect to a system that isn't in your directory?
Yes. If the system can send an outbound webhook with a JSON payload, you can use it to trigger workflows in Flows360, even if it does not have a dedicated connector.
- Auth method: Webhook URL
- Required scopes: 1
- Supported objects: 3
- Supported actions: 2
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.
Setup steps
1. In your Flows360 account, create a new workflow and select "Inbound Webhook" as the trigger.
2. Upon creation, Flows360 will generate a unique URL. Copy this URL.
3. In your external application (the source system), navigate to the webhooks or API settings section.
4. Paste the copied URL into the appropriate field for a new webhook endpoint.
5. 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).
6. Send a test request from the source system to the webhook URL.
7. 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).
8. Activate your workflow. It will now run automatically each time the source system sends data to the webhook URL.
Required scopes
]
Supported objects
- payload
- ACCOUNTS
- CONTACTS
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.
Use cases
- Marketing Automation
- Revenue Operations
- CRM to ERP Sync
- Support Ticket Sync
- Data Warehousing
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).
