# How to use the Inbound Webhook trigger for workflows

> Find out how to use the Inbound Webhook trigger to import data from external systems and automate your Futuria CRM workflows in real time.

Author: Futuria Support Team · Published: July 3, 2026 · Reading time: 5 min read

Source: https://futuriamarketing.com/en/supporto/guida-trigger-inbound-webhook-workflow/

---

## What is an Inbound Webhook?

An Inbound Webhook is a powerful feature that makes it easy to transfer data automatically from external systems into your CRM, improving integration and interoperability. When an event occurs in an external system, an HTTP request (POST, GET or PUT) is sent to a specific URL linked to a trigger in your CRM, starting a workflow.

This real-time data transfer capability strengthens your CRM's functionality and streamlines workflows across a range of platforms and tools.

By taking advantage of Inbound Webhooks, businesses can automate processes, reduce manual tasks and minimise human error, increasing efficiency and productivity. It also allows better collaboration between teams, since critical data is readily available and synchronised across different systems. This seamless integration ultimately improves decision-making, customer satisfaction and business performance.

### Some practical use cases

Inbound Webhooks can be used in a range of scenarios to improve CRM functionality and automate workflows. Here are some practical examples:

**E-commerce order integration:**  
Imagine you have an online shop and want to update your CRM with the details of a new order. You can set up an Inbound Webhook in your CRM to receive data from your e-commerce platform every time a new order is created.

**Integration with customer support ticketing systems:**  
Your business might use a separate ticketing system to handle customer requests. When a customer creates a support ticket, you can use an Inbound Webhook to send the ticket details to your CRM, making sure the support team has all the information it needs.

**Event registration integration:**  
If you run events and use a registration platform, you can use an Inbound Webhook to send attendee registration information to your CRM.

**Lead capture from web forms:**  
Inbound Webhooks can capture leads from web forms on your site or landing pages and send the data to your CRM. That way, your sales team can follow up on the lead promptly.

## How do you use the Inbound Webhook trigger for workflows?

In short, you can import your data into the system in 3 simple steps using the Inbound Webhook trigger.

![3-step overview of the Inbound Webhook trigger.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/e7f7bc8e-9c00-4d32-9ec9-b9883577bffa.png)

#### Step 1

Retrieve the webhook URL and use it in your application or system. Then send the data to the webhook URL using the appropriate HTTP request method (POST, GET or PUT) and click the "Test the trigger" button.

![Copying the webhook URL and testing the trigger in Futuria CRM.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/eb68a34d-23dd-4ac8-b564-7b00e220fe8b.jpg)

#### Step 2

Choose the data received from your application or system and save it as sample data for future reference. Click "Load more" to see more recent data. Once you have selected the data you want, save the trigger.

In this step, you can save the data reference for custom values, which can be handled in a similar way to other contact custom fields or to account-level custom values.

**Step 2.1:** Send a supported HTTP request (POST, GET or PUT) to the webhook URL you copied and copy the ID in the response.

![Sending an HTTP request to the webhook and copying the response ID.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/13eb9619-7477-40f4-af6f-1193a03aee34.jpg)

**Step 2.2:** Copy the unique ID obtained from the HTTP request and use it to search for the relevant mapping reference inside your webhook trigger.

Remember that the most recent request will always be at the top of the list.

![Searching for the reference mapping using the unique ID in the webhook trigger.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/3fa2130a-e7e7-4ee7-b25f-eae9d95a8674.gif)

**Step 2.3:** Select the correct reference and check the request body.

![Selecting the correct reference and checking the request body.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/d5145cdb-41c2-466c-918f-3eacefc20780.png)

#### Step 3

Once you have saved the trigger, you will be taken to the "Create/Update Contact" action. From there, you can select the fields you need and map the incoming data you received from the trigger.

To create a new contact or map the data onto an existing one, **you must provide an email or phone field**. If your trigger data does not contain an email or phone number, you can remove this action from the workflow, which will continue to run without an associated contact.

![Mapping incoming data in the workflow's 'Create/Update Contact' action.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/099615e4-f1ba-4205-8b9f-3133f8a12514.jpg)

Having completed the previous steps, you can now use the data received inside the workflow as custom values in emails, SMS, If/Else conditions and so on.

![Using the data received from the webhook as custom values in the workflow.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/2cf83db1-659e-4ac7-86b6-be343eb63c8d.png)

### Example of how to use the data

Inbound Webhook custom values can be used in every action inside your workflow. Here are some examples.

#### In communication actions:

![Example of using webhook custom values in a communication action.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/833a46ae-00d7-418a-a574-5220c3d44664.gif)

#### In If/Else actions:

![Example of using webhook values in an If/Else condition.](https://assets.cdn.filesafe.space/jOFcdS1QIxGsOiKRyQti/media/b5e0ff33-c783-4617-a58b-f0013c9a8763.gif)

As shown above, you can use Inbound Webhook values inside all the other actions however you see fit.

## FAQ

##### Can a workflow run without a contact?

- Yes, a workflow can run without depending on contact data. You can send any data payload through Inbound Webhook triggers and use it in the workflow.
- You can proceed without a contact and use actions that do not depend on contact information, such as custom Webhooks, Google Sheet, Slack, ChatGPT and all the internal tools.
- If you need to, you can use the "Create/Update Contact" or "Find Contact" actions to retrieve contact data in the workflow.

##### Important points to consider

- Always send the request using a supported method (POST, GET or PUT) when interacting with the webhook.
- Make sure the data is sent as a **JSON object**, the only supported data format.
- To be populated correctly, keys must be a single string with no spaces; consider using CamelCase or snake\_case.
- Providing an **email address or a phone number** in the payload is mandatory if the workflow requires contact information to find or create a contact.
- Arrays are not supported in custom values. You can send them in the request but you cannot use them inside actions.
- If the structure of your data changes, select the mapping reference again in the Inbound Webhook trigger configuration so the fields are mapped correctly in the other actions.
- If your Inbound Webhook trigger URL is compromised, delete the existing trigger and add a new one. A new URL will be generated; update your integrations to match the new URL.