Sperse

Overview

Connect Sperse with Flows360

Sperse CRM enables secure payment processing and affiliate marketing for online businesses

Use the Sperse 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 6 actions and 3 triggers.

Available actions

• Add or Update Contact
• Add or Update Contact (Extended)
• Add or Update Subscription
• Create Invoice
• Create Product
• Get Contact Details

Available triggers

• New Lead
• New Payment
• New Subscription

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: Sperse
• Package: @activepieces/piece-sperse@0.1.7
• Exact artifact digest: sha256:3fb7bb96ac4c1dcb6cc64f42dafd40e87d61b947d4660dea62af72a4afc6f904
• 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 or Update Contact (addOrUpdateContact), Creates a new contact. Classification: read.
• Add or Update Contact (Extended) (addOrUpdateContactExtended), Adds or updates a contact (extended version) Classification: read.
• Add or Update Subscription (addOrUpdateSubscription), Creates a new subscription. Classification: read.
• Create Invoice (createInvoice), Creates a new invoice in the CRM. Classification: read.
• Create Product (createProduct), Creates a new product in the CRM Classification: read.
• Get Contact Details (getContactDetails), Get Contact Details Classification: read.

Trigger contracts

• New Lead, webhook.
• New Payment, webhook.
• New Subscription, webhook.

Verification

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

Capability summary

Authentication

Authentication method: custom

Authentication profiles

Supported objects

Triggers

Setup

Setup

1. Add the Sperse 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:

• Base URL (base_url), required.
• Secret API Key (api_key), 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-sperse@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 6 actions and 3 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

Related documentation