Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Instasent

Instasent integration for Flows360 workflows.

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

Overview

Connect Instasent with Flows360

Instasent integration for Flows360 workflows.

Use the Instasent 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

  • Add/Update contact
  • Delete Contact
  • Add 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: Instasent
  • Package: @activepieces/piece-instasent@0.1.6
  • Exact artifact digest: sha256:a8a20f37e047a6bac16dd8bc208f8838c23cccf307d0cce7d7971b41743c66ce
  • 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

  • Add/Update contact (add_or_update_contact), Add or update a single contact Classification: read.
  • Delete Contact (delete_contact), Delete a single contact by User ID Classification: read.
  • Add Event (add_event), Add a contact 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
  • Project ID Required · protected credential
  • Datasource ID Required · protected credential
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add/Update contact Yes No Add or update a single contact
Delete Contact Yes No Delete a single contact by User ID
Add Event Yes No Add a contact event

Supported actions

Add/Update contact · Read

Add or update a single contact

add_or_update_contact · Risk: low · Retry: safe

Inputs

  • contact · object · Required, Enter the contact properties, the User ID is mandatory
  • instant · boolean · Optional, Process contact immediately instead of queuing. Only enable this when you need to add an event for this contact in the next step. Not recommended for high-volume operations.
Delete Contact · Read

Delete a single contact by User ID

delete_contact · Risk: low · Retry: safe

Inputs

  • userId · string · Required, Unique identifier of the contact to delete
Add Event · Read

Add a contact event

add_event · Risk: low · Retry: safe

Inputs

  • user_id · string · Required, Unique identifier of the user
  • event_id · string · Required, Unique identifier for this event. Used for deduplication.
  • event_date · string · Optional, Date and time when the event occurred, will default to now (ISO 8601 format YYYY-MM-DDTHH:MM:SS.SSSZ)
  • event_type · string · Required, Select the type of event to create
  • event_parameters · object · Required, Parameters for the selected event type

Setup

Setup

  1. Add the Instasent 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:
  • Project ID (projectId), required; stored as a sensitive connection value.
  • Datasource ID (datasourceId), required; stored as a sensitive connection value.
  • API Key (apiKey), required; stored as a sensitive connection value.
  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-instasent@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 Instasent 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-instasent@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