Asset Activation Pending (Trigger)

Written By GoCSM

Last updated 2 days ago

Overview

The Asset Activation Pending trigger activates when a customer creates an asset but does not complete the setup within a defined number of days.

This is one of the earliest signs that a customer may be stuck during onboarding. They showed intent by creating something but did not finish configuring it.

This trigger helps you step in at the right time before the customer abandons the feature.

How the Trigger Works

When a customer creates an asset such as a workflow, calendar, product, or domain but does not activate it within your defined timeframe, the workflow is triggered.

Once triggered, your workflow can:

  • Notify your team

  • Send setup guidance to the customer

  • Tag the account for follow up

Trigger Filters

Filters give you control over which pending assets activate this trigger and how often it fires. There is one required Primary Filter and several optional Additional Filters.

Primary Filter

Activation Pending Days (Required)

Sets the inactivity threshold. How long an asset must remain unactivated before the trigger fires.

Option

Description

Exactly X days

Fires only when the asset has been pending for exactly the selected number of days.

More than X days

Fires when the asset has been pending for longer than the selected number of days.

Available values: 3, 5, 7, 14, 30 days

Tip: Use Exactly when you want tightly timed touchpoints, such as a reminder on day 3 and another on day 7. Use More than when you want to catch anything that has been sitting unactivated beyond a threshold, regardless of exactly how long.

Additional Filters

These filters are optional and can be combined to narrow down which pending assets qualify and how often the trigger repeats.

Features

Limits the trigger to assets of a specific type. This allows you to build feature-specific onboarding workflows with messaging tailored to that asset.

Available options:

  • Calendars

  • Email Domains

  • Payment Products

  • Phone Numbers

  • Workflows

For example, you could create one workflow that fires when a calendar has not been activated after 5 days, and a separate workflow for unactivated payment products after 7 days, each with guidance specific to that feature.

Revisit Interval

Controls how often this trigger can fire for the same account if the asset remains unactivated. This prevents the workflow from firing repeatedly in a short period of time.

Option

Description

7 / 15 / 30 / 60 / 90 days

The trigger will not fire again for the same account until the selected number of days has passed since the last execution.

Required Setup: Find Contact Step

The trigger includes account and owner information, but the workflow still needs to identify the correct contact in your CRM.

The Find Contact step performs this mapping.

It works by taking a unique identifier from the trigger event, usually the owner’s email, and matching it to a contact record in your system.

Example setup:

Field: Email

Value: {{asset_activation_pending.ownerEmail}}

This step is important because it connects product activity to the correct contact. Without it, the system cannot send messages or apply updates to the right person.

How to Build a Workflow Using This Trigger

  1. Create a new workflow

  2. Select Asset Activation Pending as the trigger

  3. Configure the Activation Pending Days primary filter

  4. Apply any additional filters to target specific features or control retrigger frequency

  5. Add the Find Contact step using the owner email {{asset_activation_pending.ownerEmail}}

  6. Add actions such as emails, SMS, or internal notifications

  7. Publish the workflow

Recommended Uses

  • Send onboarding reminders when assets remain unactivated after 3 or 5 days

  • Build feature-specific onboarding workflows. Separate flows for calendars, phone numbers, payment products, and more, each with setup guidance tailored to that feature

  • Notify your Customer Success team to personally assist accounts that are stuck during setup

  • Route priority accounts with pending assets to a CSM for manual outreach

  • Use the More than option to catch long-stalled assets that may have been forgotten entirely