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.
