Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

DigitalPilot

DigitalPilot integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect DigitalPilot with Flows360

DigitalPilot integration for Flows360 workflows.

Use the DigitalPilot connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 2 triggers.

Available actions

  • Add Target Account
  • Remove Target Account

Available triggers

  • New High Intent Visit
  • New Target Account Visit

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: DigitalPilot
  • Package: @activepieces/piece-digital-pilot@0.1.7
  • Exact artifact digest: sha256:dc39433e9415b68038ec49cd0add67b383cebf253e6afdcd98180428da3020a6
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Target Account (add_target_account), Add a target account to a list Classification: read.
  • Remove Target Account (remove_target_account), Remove a target account from a list Classification: read.

Trigger contracts

  • New High Intent Visit, webhook.
  • New Target Account Visit, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects4
Supported actions2
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Target Account Yes No Add a target account to a list
Remove Target Account Yes No Remove a target account from a list
New High Intent Visit Yes No webhook trigger declared by the pinned package.
New Target Account Visit Yes No webhook trigger declared by the pinned package.

Supported actions

Add Target Account · Read

Add a target account to a list

add_target_account · Risk: low · Retry: safe

Inputs

  • tagId · string · Required, The ID of the tag
  • listId · string · Required, The ID of the list
  • domain · string · Required, Account domain name (e.g., example.com)
Remove Target Account · Read

Remove a target account from a list

remove_target_account · Risk: low · Retry: safe

Inputs

  • tagId · string · Required, The ID of the tag
  • listId · string · Required, The ID of the list
  • domain · string · Required, Account domain name (e.g., example.com)

Triggers

New High Intent Visit · Webhook

Triggers when a business exhibits high intent behavior on your website

Inputs

  • tagId · string
New Target Account Visit · Webhook

Triggers when a business you've identified as a high-priority target account browses your site

Inputs

  • tagId · string

Setup

Setup

  1. Add the DigitalPilot connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-digital-pilot@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required DigitalPilot connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-digital-pilot@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com