Skip to content
Book a demo
Open the menu Close the menu
Call us 06 59 01 09 31 Book a demo

HTTP and webhooks

Any API, any tool, connected to your email

No dedicated integration for your tool? Call its REST API from a workflow, with the secret stored once in a connection. And let any tool that can send a POST request start a workflow.

Connection
API key or token
Triggers
1
Actions
1
Book a demo Read the setup guide
Push a lead to your CRM Hover a node to see its role · Drag to move the graph
Email receivedEmail receivedEmail receivedExtractExtractExtractModelHTTP requestHTTP requestHTTP request
Push a lead to your CRM

What you can automate with HTTP and webhooks

Triggers

What starts a workflow.

Actions

What a workflow can do next.

  • HTTP request

    Calls an external API and puts the response into the working data.

Workflows you can build

Each one starts from a real situation and uses only nodes that exist today. Test it on past emails before you publish it.

  • Push a lead to your CRM

    The contact’s details are extracted from the enquiry and sent to your CRM’s API.

    1. Email received
    2. Extract
    3. HTTP request

  • Answer a web form by email

    Your site posts each form to the workflow, which drafts a reply from the mailbox you choose.

    1. Webhook received
    2. Compose (AI)
    3. Send as draft

  • Check your own system before replying

    The order status is read from your API and used to write an accurate reply.

    1. Email received
    2. Extract
    3. HTTP request
    4. Compose (AI)
    5. Send as draft

How to connect HTTP and webhooks

Store the API secret once in an API key connection: the server applies it at call time, and it never appears in a workflow, a run or a log.

Before you start

  • For a protected API: its key, token or credentials, and how it expects to receive them.
  • For the webhook trigger: a published workflow, whose URL you give to the calling tool.

The full guide in the documentation

  1. Open Connections and add an API key (HTTP) connection: a header key, a bearer token, a username and password, or a URL parameter.
  2. Add an HTTP request node, enter the method and URL, and pick the connection.
  3. To be called instead, start the workflow with a Webhook received trigger and give its URL to the calling tool.

See also

Related integrations

See all integrations

Automate HTTP and webhooks with Loop & Roll

We build the workflow around your processes, test it on your past emails and put it into service with your teams.

Book a demo Ask to be called back 06 59 01 09 31