Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Respond.io

Respond.io integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Respond.io with Flows360

Respond.io integration for Flows360 workflows.

Use the Respond.io 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 9 actions and 7 triggers.

Available actions

  • Add Comment to Conversation
  • Add Tag to Contact
  • Assign or Unassign Conversation
  • Create Contact
  • Create or Update Contact
  • Delete Contact
  • Find Contact
  • Open Conversation
  • Plus 1 additional declared action.

Available triggers

  • Contact Tag Updated
  • Contact Updated
  • Conversation Closed
  • Conversation Opened
  • New Contact
  • New Incoming Message
  • Plus 1 additional declared trigger.

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: Respond.io
  • Package: @activepieces/piece-respond-io@0.2.0
  • Exact artifact digest: sha256:58c147e29a48b0dd3772a73442b2aaba722c0b5517746d25f77b8295836e3502
  • 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 Comment to Conversation (add_comment_to_conversation), Add an internal comment/note to a conversation in Respond.io. Classification: read.
  • Add Tag to Contact (add_tag_to_contact), Add one or multiple tags to a contact in Respond.io. Classification: read.
  • Assign or Unassign Conversation (assign_or_unassign_conversation), Assign or unassign a conversation to/from a team member in Respond.io. Classification: read.
  • Create Contact (create_contact), Create a new contact record in Respond.io. Classification: read.
  • Create or Update Contact (create_or_update_contact), Create a new contact or update an existing one by email, phone, or ID. Classification: read.
  • Delete Contact (delete_contact), Permanently delete a contact from Respond.io. Classification: read.
  • Find Contact (find_contact), Search for contacts by name, email, or phone number in Respond.io. Classification: read.
  • Open Conversation (open_conversation), Mark a conversation as open in Respond.io. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Contact Tag Updated, webhook.
  • Contact Updated, webhook.
  • Conversation Closed, webhook.
  • Conversation Opened, webhook.
  • New Contact, webhook.
  • New Incoming Message, webhook.
  • New Outgoing Message, webhook.

Verification

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

Capability summary

Authenticationcustom
Supported objects16
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Comment to Conversation Yes No Add an internal comment/note to a conversation in Respond.io.
Add Tag to Contact Yes No Add one or multiple tags to a contact in Respond.io.
Assign or Unassign Conversation Yes No Assign or unassign a conversation to/from a team member in Respond.io.
Create Contact Yes No Create a new contact record in Respond.io.
Create or Update Contact Yes No Create a new contact or update an existing one by email, phone, or ID.
Delete Contact Yes No Permanently delete a contact from Respond.io.
Find Contact Yes No Search for contacts by name, email, or phone number in Respond.io.
Open Conversation Yes No Mark a conversation as open in Respond.io.
Custom API Call Yes No Make a custom API call to a specific endpoint
Contact Tag Updated Yes No webhook trigger declared by the pinned package.
Contact Updated Yes No webhook trigger declared by the pinned package.
Conversation Closed Yes No webhook trigger declared by the pinned package.
Conversation Opened Yes No webhook trigger declared by the pinned package.
New Contact Yes No webhook trigger declared by the pinned package.
New Incoming Message Yes No webhook trigger declared by the pinned package.
New Outgoing Message Yes No webhook trigger declared by the pinned package.

Setup

Setup

  1. Add the Respond.io 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:
  • API Token (token), 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-respond-io@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 9 actions and 7 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 Respond.io 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-respond-io@0.2.0 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