During the execution of your plan, you can create a task to send HTTP requests to a third-party application endpoint. For example, when a flow task successfully executes, you can send an HTTP message to a designated endpoint.



NOTE: It's possible that webhook requests can be submitted back to the platform to execute API tasks within the platform. However, there are security concerns. Additional configuration is required. For more information, see Configure Webhooks.

Requirements for receiving application

To send an HTTP request to a target application, the application must be configured to receive the request:


  1. Open your plan in Plan View. Click a node to create a new task.

  2. In the right panel, select HTTP task.

  3. Set the following parameters:

    NameUser-visible name of the task.
    UrlURL where the webhook message is received by the other application.

    Insert HTTP content headers as key-value pairs. For example, if your body is in JSON format, you should include the following header:

    key: Content-Type
    value: application/json

    NOTE: You may be required to submit an authentication token as the value for the Authorization key.

    Please refer to the documentation for your receiving application about the required headers.


    (POST, PUT, or PATCH methods only) The body of the request submitted to the receiving application.

    NOTE: If your request does not require a body, please insert {} here. This is a known issue.

    MethodSelect the HTTP method to use to deliver the message. The appropriate method depends on the receiving application. Most use cases require the POST method.
    Secret key

    (Optional) A secret key can be used to verify the webhook payload. This secret value must be inserted in this location, and it must be included as part of the code used to process the requests in the receiving application. Insert the secret value here as a string without quotes.

    For more information on how this secret key is used to generate a signature, see Verify Webhook Signatures below.

    Validate SSL certificate

    When set to true, HTTPS (SSL) communications are verified to be using a valid certificate before transmission.

    NOTE: If you must send a request to an endpoint that has an expired/invalid certificate, you must disable SSL verification.

    Retry on failure

    If the returned status code is outside of the 200-299 range, then the webhook is considered to have failed. When this option is enabled, the request is retried.

    When a message is retried, the following header is submitted:

  4. To test the connection, click Test. A success message is displayed.
  5. To add the task to the flow, click Save.


Run another job

You can create a task to run another job on the successful execution of this one.

Tip: Use this method to create conditional sequences of job executions.

As needed, you can specify task overrides as part of a launching a job via API. For more information, see API Workflow - Run Job.


NOTE: For this example, the platform must be whitelisted to receive requests from itself. Additional configuration is required. For more information, see Configure Webhooks.

You must acquire the recipe identifier for the next job to execute. 

  1. Open the flow containing the next recipe. 
  2. In Flow View, click the recipe whose outputs you wish to generate. 
  3. Review the URL for the recipe object. In the example below, the recipe Id value is 4:

  4. Retain this value for below.

Define the HTTP task


This name appears in the only.


Specify the URL as follows, replacing the example values with your own:


Insert the following two headers:

key: Content-Type
value: application/json
key: Authorization
value: Bearer <paste your access token here>

NOTE: The token value must be preceded by the string: Bearer.


In the body, insert the recipe Id for the value for wrangledDataset, which is the internal platform term for recipe:

  "wrangledDataset": {
    "id": 4

MethodSelect the POST method.


  1. Run the plan for which the HTTP task was created.
  2. When the plan successfully completes, open the flow containing the other job to execute. 
  3. When you select the target recipe, a new job should be queued, in-progress, or completed.

Slack channel message

Tip: Slack tasks are now a supported product feature. For more information, see Create Slack Task.

You can create an HTTP task to deliver a text message to a Slack channel of your choice.


Set up your Slack installation to receive HTTP messages:

  1. If needed, create a Slack channel to receive your messages.
  2. Create an app.
  3. Activate incoming HTTP messages for your app. 
  4. Specify the channel to receive your incoming messages.
  5. Copy the URL for the incoming HTTP request from the cURL statement.

Define the HTTP task


This name appears in the only.

MethodSelect the POST method.
UrlPaste the URL that you copied from Slack.
Copy the content headers from the Slack cURL command:
key: Content-Type
value: application/json
{"text":"Your job has completed."}


  1. Click Test to validate that this task will work. 
  2. Run a job:
    1. Check the Slack channel for a message.

Plan metadata examples

You can reference metadata information from the plan definition and the current plan run as part of the request of your HTTP task. 



A plan metadata reference is constructed using the following syntax. In the appropriate textbox, enter one of the following values:

Tip: Start by typing $, which provides access to a menu tree of metadata references for each of the metadata reference types. The final syntax is noted above.

Entered valuePlan metadata reference type
Metadata information from the plan definition or the current plan run.
Metadata information for the flow tasks executed in the current plan run.
{{$flow_7p.['My Output Name'].

Metadata information for the outputs generated by the specific flow task. In this example:

  • flow_7p is a reference to the specific flow task.
  • 'My Output Name' is the display name for the underlying output.

Plan information

The following request body contains references to the Plan name, plan run identifier, and the flow that was just executed:

{"text":"Plan: {{$plan.name}} 
RunId: {{$plan.runId}}
Flow: {{$flow_7p.name}}

Plan run information

The following request body contains plan execution information using timestamps:

{"text":"Plan: {{$plan.name}} 
RunId: {{$plan.runId}}
- plan start: {{$plan.startTime}}
Running time: {{$plan.duration}}

- last task start: {{$flow_7p.startTime}}
- last task end: {{$flow_7p.endTime}}

HTTP task information

You can reference information from an HTTP task that has already occurred:

{"text":"{{$http_qg.name}} returned {{$http_qg.statusCode}}."} 

Flow task information

The following request body references information from a flow task in the plan:

{"text":"{{$flow_7p.name}} execution:
Duration: {{$flow_7p.duration}}
Status: {{$flow_7p.status}}

For more information, see jobIds: {{$flow_7p.jobIds}}

Flow information

The following request body references information from the underlying output for the above flow task:

{"text":"Flow reference information:
Name: {{$flow_7p['2013 POS'].name}}
Favorite column: {{$flow_7p['2013 POS'].columns.Store_Nbr.name}} 
Least favorite data source: {{$flow_7p['2013 POS'].sources['POS-r01.txt'].name}}
For more information, see jobIds: {{$flow_7p.jobIds}}


For more information, see Plan Metadata References.

Feed metadata inputs to cloud function

This example demonstrates how you can use an HTTP task to deliver plan metadata to AWS lambda functions. A similar approach could be used for Google Cloud functions.

In this case, the rowCount value from the flow task execution is delivered via HTTP task to an AWS lambda function.

General steps:

  1. Define your plan.
  2. Flow task: Run the flow to generate the outputs needed for your Lamda function.
  3. HTTP task: generates an HTTP request whose body includes a reference to the rowCount metadata variable. Request body:

     "rowCount": "{{$flow_7p['My Flow Name'].output['My output name'].rowCount}}"
  4. AWS Lambda functions: The following is pseudo-code for Lambda:

    import json
    def lambda_handler(event, context):
      httpTaskBody = json.loads(event["body"])
      rowCount = httpTaskBody["rowCount"]
      return {
        'statusCode': 200,
        'body': json.dumps(rowCount)
  5. Google Cloud functions: The following is pseudo-code for Google Cloud functions:

    def get_row_count(request):
      request_json = request.get_json()
      if request_json and 'rowCount' in request_json:
      	rowCount = request_json['rowCount']
        return rowCount
      return 'No rowCount attribute provided'

Verify Signatures

Depending on the target application, implementing signature verification may require developer skills.

Optionally, you can configure the platform to sign the HTTP requests sent for a flow. Signed requests guarantee that the requests are sent from the platform, instead of a third party.

Below, you can review how the signature is created, so that you can configure the receiving application to properly process the signature and its related request.

Signature Header

HTTP requests are signed by inserting the X-Webhook-Signature header in the request. These signatures are in the following form:

X-Webhook-Signature: t=<timestamp>,sha256=<signature>


More information on these values is available below.


X-Webhook-Signature: t=1568818215724,sha256=55fa71b2e391cd3ccba8413fb51ad16984a38edb3cccfe81f381c4b8197ee07a

Check Application Tools

Depending on the application, you may need to complete one of the following sets of tasks to verify the task signatures:

NOTE: You may need to whitelist the platform in your application. See the application's documentation for details.

You may be required to create some custom coding for your application. Below, you can review details on how to do so, including a JavaScript example.

Process Signed Requests


The timestamp value (t=<timestamp>) appears at the beginning of the header value to prevent replay attacks, where an attacker could intercept a valid payload and its signature and re-transmit them.


The task signature includes as part of its hashed value:

Step 1 - Extract the timestamp and signatures

Split the X-Webhook-Signature header:

  1. Split values using the , character as a separator. 
  2. Split each of the parts using the = character.
  3. Extract the values for the timestamp and signature. From the above example:
    1. timestamp: 1568818215724
    2. signature: 55fa71b2e391cd3ccba8413fb51ad16984a38edb3cccfe81f381c4b8197ee07a

Step 2 - Create the expected signature

In the receiving application, you can recompute the signature to verify that the request was sent from the platform.

  1. Concatenate the timestamp, the dot character and the request body (POST/PUT/PATCH methods) or the url (GET/DELETE methods).
  2. Suppose the above example is the signature for a POST request, and the request body is test. The concatenated value is the following:

  3. You can now compute the HMAC authentication code in your receiving application. In the following JavaScript example, the secret key value is mySecret:

    const crypto = require('crypto');
    const message = '1568818215724.test'; // as defined above
    const hmac = crypto.createHmac('sha256', 'mySecret');
    const expectedSignature = hmac.digest('hex');

Step 3 - Compare the signatures

The value returned by your code and the value included as the signature in the X-Webhook-Signature header should be compared: