Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Salsa

Salsa integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.2
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Salsa with Flows360

Salsa integration for Flows360 workflows.

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

  • Get supporters
  • Upsert Supporter on Email
  • Upsert Offline Donation

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: Salsa
  • Package: @activepieces/piece-salsa@0.1.2
  • Exact artifact digest: sha256:0c3e16f28498ba58b444562ee4cd439e388e7caf6686acfe0cf3bc24cff6062c
  • 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

  • Get supporters (supporter-search), Get all supporters after date Classification: read.
  • Upsert Supporter on Email (supporter_upsert), Upsert Supporter based on Email Classification: read.
  • Upsert Offline Donation (offline_donation_upsert), Upsert Offline Donation based on Email Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects3
Supported actions3
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get supporters Yes No Get all supporters after date
Upsert Supporter on Email Yes No Upsert Supporter based on Email
Upsert Offline Donation Yes No Upsert Offline Donation based on Email

Supported actions

Get supporters · Read

Get all supporters after date

supporter_search · Risk: low · Retry: safe

Inputs

  • baseUrl · string · Required, API url acquired from your Salsa API
  • identifiers · array · Optional, Filters results based on the ID for the supporters
  • identifierType · string · Optional, Select the object
  • searchString · string · Optional, The value to search for if identifierType is SEARCH_STRING. If you provide 2 words separated by a space, it will search first and last names respectively. A single search term will search first name, last name and email
  • modifiedFrom · string · Required, Starting date time to base a search
  • modifiedTo · string · Optional, End date time for a search. Optional and if not provided defaults to now
  • offset · number · Optional, Starting index to retrieve values from. This allows you to paginate larger results set
  • count · number · Optional, The maximum number of items to retrieve.
  • includeCellOnly · boolean · Optional, Should cell-phone only supporters be included in the results
  • includeNormal · boolean · Optional, Should normal supporters be included in the results
Upsert Supporter on Email · Read

Upsert Supporter based on Email

supporter_upsert · Risk: low · Retry: safe

Inputs

  • baseUrl · string · Required, API url acquired from your Salsa API
  • supporters · object · Required, The Supporters JSON Array
Upsert Offline Donation · Read

Upsert Offline Donation based on Email

offline_donation_upsert · Risk: low · Retry: safe

Inputs

  • baseUrl · string · Required, API url acquired from your Salsa API
  • donations · object · Required, The Offline Donation JSON Array

Setup

Setup

  1. Add the Salsa 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-salsa@0.1.2; 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Salsa 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-salsa@0.1.2 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