Business Event node

The Business Event trigger allows users to launch a workflow without the customer context. This way users get an opportunity to create a new type of workflows. The Business Event can be used to receive information about the product storage changes, price changes, and so on. If the data sent to the system contains a customer ID, you can also transform a joruney into customer-oriented one and send events by means of the Outgoing Webhook node.

Important: Customer-oriented nodes cannot be used in an automation triggered by a business-oriented node.

What is it


Business Event allows users to create workflows without customer-related data, based only on the input data. This way you can automate your business activities and build integrations between them.

Prerequisites


Prepare the Incoming webhook integration.

How it works


  1. Click the pencil icon on the Business Event node.
    Result: A pop-up opens.
  2. From the Incoming webhook dropdown, select the incoming integration you have prepared before.
  3. If

    If you want to monitor the entries into this step, switch the Track datapoints toggle on. As a result, events related to the movement between nodes (automation.clientPathStep) will be available in the Analytics module to use. These events (automation.clientPathStep, automation.clientEndStep, automation.startPath) are displayed on the activity list on the profile card regardless of the configuration of this option.

  4. Confirm by clicking Apply.

Example of use


Example of use
Example of a workflow
Tip: You can check how the Business Event node is used in the use case concerning integration of Microsoft Azure Forms with Synerise.

The aim of the workflow is to receive data that contains indirect customer information and then to process and to transform the data in such a way that further actions become customer oriented.

  1. Add a Business Event trigger node.

  2. Use the incoming webhook integration by means of which the system receives data about products in the cart and the email as the identifier.

  3. Connect the Business Event trigger node with the Outgoing Integration node. The body transferred from the Incoming webhook selected in the Business Event is passed to an endpoint. In this example, the Incoming webhook uses the endpoint documented here. To pass further the values received in the Incoming webhook, you can use jinja.

    {{request.body.paramName}} for the parameters in the request body
    {{request.headers.headerName}} for the parameters in the request headers

    Below you can find an example of data received from the external service to an endpoint indicated in the Incoming webhook settings.

    {
        "body": {
        "parameter1": "value1"
    },
    "businessProfileId": 611,
    "endpointId": "XXXX-XXXX-XXXX-XXXX-XXXXXXXXXX",
    "eventId": "XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
    "headers": {
    "X-Request-ID": "XXXXXXXXXXXXXXXXXXX",
    "X-Forwarded-Host": "example host",
        },
    "method": "POST",
    "time": 1583206296408
    }
    • To pass the value of parameter1, in the body of the Outgoing Integration enter:
      {{request.body.parameter1}}
    • To pass the value of the X-Request-ID header, in the body of the Outgoing Integration enter:
      {{request.headers["X-Request-ID"]}}
      Result: A new event appears on the activity list on the customer card.
  4. Connect the Outgoing Integration with the End node.

😕

We are sorry to hear that

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

😉

Awesome!

Thank you for helping improve out documentation. If you need help or have any questions, please consider contacting support.

Close modal icon Placeholder alt for modal to satisfy link checker