Configure an SQL command to update devrev objects based on actions captured in your BQ datalake.

Configure an SQL command to update DevRev objects based on actions captured in your BQ data lake.

Funnel Automations

The funnel automation snap-in allows you to configure an SQL command to update DevRev objects based on actions captured in your BigQuery data lake.```

How it works

  1. Install the snap-in.
  2. Connect the snap-in with your BQ credentials.
  3. Configure the SQL command to update. The query should return a minimum of two columns, with an optional message column. These columns are:
  • id: This should map to the DevRev ID of the object to update.
  • [field_name]: The name of the field to update, with the corresponding value to update. This must be in the API format (for example, tnt__stage for the custom field name stage or [address.city](http://address.city/) for the nested city field).
  • [message] (optional): A message to be sent to the Slack Webhook configured.
  1. Optionally, configure the Slack Webhook. This will send a message to the attached channel based on the message column in the query. See https://api.slack.com/messaging/webhooks for more info on generating webhooks.
  2. Optionally, configure the priority list. If the field being updated has an ordered set of values and you want to prevent it from being decreased by this automation, configure the priority list here. This setting applies to all fields updated by this snap-in, so for multiple fields with different priority lists, install the snap-in multiple times. For example, to advance prospects through pipeline stages (Lead -> Prospect -> User), configure the priority list as Lead,Prospect,User. This ensures values can move to User but not revert to Lead or Prospect from User.