Overview
Connect Help Scout with Flows360
Help Scout integration for Flows360 workflows.
Use the Help Scout 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 4 triggers.
Available actions
- Create Conversation
- Send Reply
- Add Note
- Create Customer
- Update Customer Properties
- Find Conversation
- Find Customer
- Find User
- Plus 1 additional declared action.
Available triggers
- Conversation Created
- Conversation Assigned
- New Customer
- Tags Updated
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: Help Scout
- Package:
@activepieces/piece-help-scout@0.2.0 - Exact artifact digest:
sha256:a8244943727b65b146b3de1dda49d51af5410952ebd7e6849c9f6ceeeb1c1f36 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
OAUTH2. 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 Conversation (
create_conversation), Start a new conversation. Classification: read. - Send Reply (
send_reply), Sends a reply in an existing conversation. Classification: read. - Add Note (
add_note), Adds a note to a conversation. Classification: read. - Create Customer (
create_customer), Adds a new customer to Help Scout. Classification: read. - Update Customer Properties (
update_customer_properties), Updates customer's properties. Classification: read. - Find Conversation (
find_conversation), Finds an existing conversation using provided filter. Classification: read. - Find Customer (
find_customer), Finds a customer by email. Classification: read. - Find User (
find_user), Finds a user by email. Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- Conversation Created, webhook.
- Conversation Assigned, webhook.
- New Customer, webhook.
- Tags Updated, 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: OAuth 2.0
Authentication profiles
connection · oauth2
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Create Conversation | Yes | No | Start a new conversation. |
| Send Reply | Yes | No | Sends a reply in an existing conversation. |
| Add Note | Yes | No | Adds a note to a conversation. |
| Create Customer | Yes | No | Adds a new customer to Help Scout. |
| Update Customer Properties | Yes | No | Updates customer's properties. |
| Find Conversation | Yes | No | Finds an existing conversation using provided filter. |
| Find Customer | Yes | No | Finds a customer by email. |
| Find User | Yes | No | Finds a user by email. |
| Custom API Call | Yes | No | Make a custom API call to a specific endpoint |
| Conversation Created | Yes | No | webhook trigger declared by the pinned package. |
| Conversation Assigned | Yes | No | webhook trigger declared by the pinned package. |
| New Customer | Yes | No | webhook trigger declared by the pinned package. |
| Tags Updated | Yes | No | webhook trigger declared by the pinned package. |
Triggers
Conversation Created · Webhook
Triggers when a new conversation is started in a mailbox.
Inputs
mailboxId· stringassignedTo· string
Conversation Assigned · Webhook
Triggers when a conversation is assigned to a user.
Inputs
mailboxId· stringassignedTo· string
New Customer · Webhook
Triggers when a new customer is added.
Tags Updated · Webhook
Triggers when tags on a conversation are modified.
Inputs
mailboxId· stringassignedTo· string
Setup
Setup
- Add the Help Scout connector to the workflow in the target Flows360 Studio instance.
- 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.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-help-scout@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 9 actions and 4 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 Help Scout 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-help-scout@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.