Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Dittofeed

Customer data platform for user analytics and tracking

CategoryMarketing
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Dittofeed with Flows360

Customer data platform for user analytics and tracking

Use the Dittofeed 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 3 actions and no declared triggers.

Available actions

  • Identify User
  • Track Event
  • Screen Event

Available triggers

  • No triggers are declared in this pinned package.

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: Dittofeed
  • Package: @activepieces/piece-dittofeed@0.1.6
  • Exact artifact digest: sha256:00d6f1f0d908c7b4c552156e1d58c8f5e504dbe09b616dd6e1d60263a68cc4c6
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Identify User (identify), Identify a user in Dittofeed. Classification: read.
  • Track Event (track), Track an event for a user. Classification: read.
  • Screen Event (screen), Track a screen view event. Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

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

Capability summary

Authenticationcustom
Supported objects3
Supported actions3
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential
  • Base URL Required

Supported objects

ObjectReadWriteNotes
Identify User Yes No Identify a user in Dittofeed.
Track Event Yes No Track an event for a user.
Screen Event Yes No Track a screen view event.

Supported actions

Identify User · Read

Identify a user in Dittofeed.

identify · Risk: low · Retry: safe

Inputs

  • userId · string · Required
  • traits · object · Optional
Track Event · Read

Track an event for a user.

track · Risk: low · Retry: safe

Inputs

  • userId · string · Required
  • event · string · Required
  • properties · object · Optional
Screen Event · Read

Track a screen view event.

screen · Risk: low · Retry: safe

Inputs

  • userId · string · Required
  • name · string · Required
  • properties · object · Optional

Setup

Setup

  1. Add the Dittofeed 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:
  • API Key (apiKey), required; stored as a sensitive connection value.
  • Base URL (baseUrl), required.
  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-dittofeed@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 actions and 0 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 Dittofeed 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-dittofeed@0.1.6 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