This article will touch on how to set up webhooks with Everflow for setting up integrations with third-party tech solutions.

Genny avatar
Written by Genny
Updated over a week ago

Updated - Feature Release 3.5.0 (February 2023):

  • Added separate (previously available in Control Center) sections titled "Integrations" and "Automation" (Scheduled Actions, Alerts, & Webhooks) in the main navigation menu (accessed through the hamburger menu icon).

Updated - Feature Release 3.4.1 (October 2023): Added webhook event for Advertiser Signed Up [Click Here]


Webhooks allow you to pass data from Everflow to external tech solutions in real time. Webhooks occur when an Event happens in Everflow and can trigger either a GET or a POST call to a specific endpoint. These are primarily used for updating data on an external tech solution or notifying someone that an Event happened.

Refer to our API documentation for more technical details - [Click Here]

A How-To Guide

Step #1

  • Navigate to Automation - Webhooks.

Step #2

  • Click [+ Add Webhook].

Step #3

  • Fill in the required fields.

Name: This is what you call the Webhook.

Status: Active or Inactive

HTTP Method: Either GET or a POST call. For more info - [Click Here]

Events: Available events that can trigger the HTTP Method.

URL: The Webhook URL that Everflow will ping when the Event happens.

Step #4

  • Click Add. Then, be sure to execute an Event to test the Webhook.

Step #5

  • Navigate back to Automation - Webhooks, and click on the Webhook Name.

  • Then, click on the Delivery Logs tab to confirm the Webhook was triggered properly. See below for details about this log.

Success: Response from your server. A Yes indicates a successful 200 or 300 response, and anything other than 200 or 300 will result in a No. There are many reasons why the receiving server would not return a 200 response, which you will need to investigate further on your end.

Response Code: From receiving server. For more info about response codes - [Click Here]

HTTP Method: Either GET or POST. We do not post a body with a GET call.

URL: The URL being called.

Payload: Click View to reveal the payload sent to the URL. This is great to use for debugging issues.

Date Delivered: Date this Webhook was sent.

Did this answer your question?