Core Docs - Engagement - Connection Workflows

Rock Version: v19.0
Last Modified: 2026-03-24 9:20 AM

On their own, the connection features are very powerful. Adding workflows to the mix, though, magnifies what you can do. Let's take a look at how you can set up workflows for your connections.

You can define workflows for your requests for the connection type (in which case they will be applied to all requests in all opportunities) or for a specific opportunity. In either case the configuration is the same.

There are two basic items that you'll need to configure: the Trigger and the Workflow Type.

Trigger

This defines when the workflow should be started. Your options are:  

Workflow Type 

This is the simple part. This defines which workflow will be executed when the trigger condition is met.  

Building Connections Workflows

When the workflows above are executed, the initial activity of the workflow will have access to the connection request through the workflow entity property. It's important that this initial activity gets the information it needs to process from the request. The main action you'll use to get the properties from the request is Attribute Set From Entity. You can use the Lava Template field of this action to pull different properties of each request. Below are a few samples:

The 'Activity Added' Workflow Trigger is a Bit Different
While most of the workflow triggers send the Connection Request to the workflow, the 'Activity Added' trigger only sends the new Activity. So, if your workflow is triggered by 'Activity Added' then you will need an extra step to get the Connection Request associated with that activity. You can derive the Connection Request from the Activity by using the following Lava:
{{ Entity.ConnectionRequest.Guid }}

Connection Attribute Types
Rock provides several attribute types to help you build workflows. These include:
- Connection Request - Set by Guid
- Connection Status - Set by Guid
- Connection State - Set by Enum value
- Connection Type - Set by Guid
- Connection Opportunity - Set by Guid
- Connection Activity Type - Set by Guid

Automatically Persist
Be cautious when disabling auto-persistence for workflows manually triggered from a connection request, as it might lead to unexpected behavior.

Connection Workflow Actions

To facilitate even more power with connections we've added several workflow actions. They're outlined below.

Create Connection Request

Creates a new connection request with the following settings.

Transfer Connection Request

Transfers a connection request to a new opportunity type.

Set Connection Request Status

Changes the status of a connection request.

Set Connection Request State

Changes the state of a connection request.

Add Connection Request Activity

Adds a new connection request activity.

See our Workflows guide for more information on working with workflows.