Respaid currently provides 10 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
New Campaign Creation Result
Triggers when the campaign is created.
New Cancelled Case
Triggers when a collection process for a given sequence (case) was cancelled.
New Disputed Case
Triggers when a collection process was disputed by the debtor.
New Payout
Triggers when a payout is successfully sent to your bank account.
New Successful Collection Paid to Creditor
Triggers when a debt is paid directly to the creditor.
New Successful Installment Payment via Respaid
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
Triggers when a debt is paid to the Legal Officer responsible for the collection campaign.
New Successful Partial Payment to Creditor
Triggers when the debt is partially paid directly to the creditor.
New Successful Partial Payment via Respaid
Triggers when the debt is partially paid via Respaid's payment link.
New Successful Collection via Respaid
Triggers when a debt is paid online via Respaid's payment link.
Create New Campaign
Action for creating a new campaign.
Stop Collection for Direct Full Payment
Stops the collection process for a case and mark it as paid directly to the creditor.
Stop Collection for Direct Partial Payment
Stops the collection process for a case and mark it as partially paid directly to the creditor.
Stop Collection for Direct Instalment Payment
Stops the collection process for a case when an instalment plan is set up with the creditor.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Respaid event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Campaign Creation Result
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Respaid action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create New Campaign
Combine Respaid with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
New Campaign Creation Result
Finishes with
Create New Campaign, then preserve the outcome in Coherence
The exact authentication fields depend on Respaid. The workflow structure stays straightforward:
Authorize the Respaid account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Respaid or provide a complementary trigger or action.
Respaid currently provides 10 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Respaid currently lists 10 triggers and 4 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Respaid triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
