Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Respaid

Respaid integration for Flows360 workflows.

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

Overview

Connect Respaid with Flows360

Respaid integration for Flows360 workflows.

Use the Respaid 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 4 actions and 10 triggers.

Available actions

  • Create New Campaign
  • Stop Collection for Direct Full Payment
  • Stop Collection for Direct Partial Payment
  • Stop Collection for Direct Instalment Payment

Available triggers

  • New Campaign Creation Result
  • New Cancelled Case
  • New Disputed Case
  • New Payout
  • New Successful Collection Paid to Creditor
  • New Successful Installment Payment via Respaid
  • Plus 4 additional declared triggers.

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: Respaid
  • Package: @activepieces/piece-respaid@0.1.6
  • Exact artifact digest: sha256:54090a9b805084c8a099dff32ee95e4851989978f7ab0e23854474cf83d0e7a7
  • 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

  • Create New Campaign (create_new_campaign), Action for creating a new campaign. Classification: read.
  • Stop Collection for Direct Full Payment (stop_collection_client_paid_directly), Stops the collection process for a case and mark it as paid directly to the creditor. Classification: read.
  • Stop Collection for Direct Partial Payment (stop_collection_for_direct_partial_payment), Stops the collection process for a case and mark it as partially paid directly to the creditor. Classification: read.
  • Stop Collection for Direct Instalment Payment (stop_collection_for_direct_instalment_payment), Stops the collection process for a case when an instalment plan is set up with the creditor. Classification: read.

Trigger contracts

  • New Campaign Creation Result, webhook.
  • New Cancelled Case, webhook.
  • New Disputed Case, webhook.
  • New Payout, webhook.
  • New Successful Collection Paid to Creditor, webhook.
  • New Successful Installment Payment via Respaid, webhook.
  • New Successful Collection via Legal Officer, webhook.
  • New Successful Partial Payment to Creditor, webhook.
  • New Successful Partial Payment via Respaid, webhook.
  • New Successful Collection via Respaid, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects14
Supported actionsNot published
Triggers10

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create New Campaign Yes No Action for creating a new campaign.
Stop Collection for Direct Full Payment Yes No Stops the collection process for a case and mark it as paid directly to the creditor.
Stop Collection for Direct Partial Payment Yes No Stops the collection process for a case and mark it as partially paid directly to the creditor.
Stop Collection for Direct Instalment Payment Yes No Stops the collection process for a case when an instalment plan is set up with the creditor.
New Campaign Creation Result Yes No webhook trigger declared by the pinned package.
New Cancelled Case Yes No webhook trigger declared by the pinned package.
New Disputed Case Yes No webhook trigger declared by the pinned package.
New Payout Yes No webhook trigger declared by the pinned package.
New Successful Collection Paid to Creditor Yes No webhook trigger declared by the pinned package.
New Successful Installment Payment via Respaid Yes No webhook trigger declared by the pinned package.
New Successful Collection via Legal Officer Yes No webhook trigger declared by the pinned package.
New Successful Partial Payment to Creditor Yes No webhook trigger declared by the pinned package.
New Successful Partial Payment via Respaid Yes No webhook trigger declared by the pinned package.
New Successful Collection via Respaid Yes No webhook trigger declared by the pinned package.

Triggers

New Campaign Creation Result · Webhook

Triggers when the campaign is created.

New Cancelled Case · Webhook

Triggers when a collection process for a given sequence (case) was cancelled.

New Disputed Case · Webhook

Triggers when a collection process was disputed by the debtor.

New Payout · Webhook

Triggers when a payout is successfully sent to your bank account.

New Successful Collection Paid to Creditor · Webhook

Triggers when a debt is paid directly to the creditor.

New Successful Installment Payment via Respaid · Webhook

Triggers when one of the installment payments is made for a given case within a collection's payment plan.

New Successful Collection via Legal Officer · Webhook

Triggers when a debt is paid to the Legal Officer responsible for the collection campaign.

New Successful Partial Payment to Creditor · Webhook

Triggers when the debt is partially paid directly to the creditor.

New Successful Partial Payment via Respaid · Webhook

Triggers when the debt is partially paid via Respaid's payment link.

New Successful Collection via Respaid · Webhook

Triggers when a debt is paid online via Respaid's payment link.

Setup

Setup

  1. Add the Respaid 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-respaid@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 10 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 Respaid 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-respaid@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