Skip to content
Elooo SystemHelp Center Go to website

Workflow builder

How to send workflow data to another system (outgoing webhook)

In the workflow, click + and add the Custom Webhook action. Paste the address (URL) that will receive the data, pick the method (POST, GET, PUT or DELETE), set the authorization if the other system requires it, and build the data to send from the contact's fields. Save the action and publish.

Updated on

Before you start

  • Have the address (URL) of the system that will receive the data. Whoever runs that system can tell you the URL, the method (usually POST) and whether it requires authorization.
  • If the destination needs a key or token, store it in a custom value under Settings › Custom Values so it isn't written in plain sight in the workflow.
  • Make sure the destination can handle the number of requests you'll send: the action fires the moment each contact reaches that step.
Where to find it

Automation › Workflows › (open the workflow) › + › Custom Webhook

Step by step

  1. Open Automation › Workflows and open the workflow (or create a new one with the trigger you need).
  2. Click the + at the point where the data should be sent and choose Custom Webhook.
  3. In URL, paste the destination address.
  4. In Method, choose what the destination expects: POST (the most common for sending data), GET, PUT or DELETE.
  5. In Authorization, choose the type the destination requires (or none) and fill in the credentials.
  6. If the destination needs them, add Headers (for example, the content type) and Query Parameters.
  7. In the data section, create one field per piece of information: type the field name (e.g. email) and pick the contact data as its value. As you type, suggestions appear with contact fields, custom values and data received through an inbound webhook.
  8. Click Save Action.
  9. Run a test contact through the workflow and confirm in the destination system that the data arrived.
  10. Publish the workflow.

Tips

  • Name the fields the way the destination expects (e.g. name, email, phone); if the names don't match, the destination may ignore the data.
  • You can send anything the workflow knows: contact data, custom fields, custom values and whatever came in through an inbound webhook.
  • To see exactly what was sent and what the destination replied, open Execution Logs inside the workflow and search for the contact.

Common problems

  • The action shows as failed in the logs → The destination replied with an error. Check the URL, method and authorization. The Elooo System retries a few times with growing intervals; if it keeps failing, the action is skipped and the contact moves on to the next step.
  • Data arrives but some fields are empty → The contact doesn't have that data filled in, or the value chosen for the field isn't the right one. Open the action and check each field.
  • Lots of errors when I add contacts in bulk → The destination has request limits. Add contacts in smaller batches or place a Wait action before the webhook.
  • The destination requires a token and I don't know where to put it → It usually goes in Authorization or in a Header (e.g. Authorization). Ask whoever runs the system which format it expects.

Frequently asked questions

What's the difference between an inbound and an outgoing webhook?

An inbound webhook is a trigger: another system sends data to the Elooo System and starts the workflow. An outgoing webhook is an action: the Elooo System sends data to another system.

Do I need to know how to code?

No. You only fill in the URL, method, authorization and the fields to send. The technical part (what the destination expects) comes from whoever runs that system.

Was this helpful?