Skip to content
← Back to documentation
Technical Reference

Front

Front integration for Flows360 workflows.

CategoryCustomer Support
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Front with Flows360

Front integration for Flows360 workflows.

Use the Front 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 21 actions and 5 triggers.

Available actions

  • Add Comment
  • Add Contact Handle
  • Add Conversation Links
  • Add Conversation Tags
  • Assign/Unassign Conversation
  • Create Account
  • Create Contact
  • Create Draft
  • Plus 13 additional declared actions.

Available triggers

  • New Comment
  • New Inbound Message
  • New Outbound Message
  • New Tag Added to Message
  • New Conversation State Change

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: Front
  • Package: @activepieces/piece-front@0.2.0
  • Exact artifact digest: sha256:cbb93613e7a9b3bd3d42027e0e8c72c3249608f06846f99bda023861359fc18b
  • 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

  • Add Comment (addComment), Add a comment (internal note) to a conversation in Front. Classification: read.
  • Add Contact Handle (addContactHandle), Add a handle (email, phone number, etc.) to an existing Contact. Classification: read.
  • Add Conversation Links (addConversationLinks), Link external references (URLs) to a conversation. Classification: read.
  • Add Conversation Tags (addConversationTags), Add one or more tags to a conversation. Classification: read.
  • Assign/Unassign Conversation (assignUnassignConversation), Assign a conversation to a teammate or remove assignment. Classification: read.
  • Create Account (createAccount), Create a new account in Front. Classification: read.
  • Create Contact (createContact), Create a new contact in Front. Classification: read.
  • Create Draft (createDraft), Create a draft message in Front. Classification: read.
  • Create Draft Reply (createDraftReply), Create a draft reply to an existing conversation (subject/quote etc.) without sending immediately. Classification: read.
  • Create Link (createLink), Create a Link in Front (name, external URL). Classification: read.
  • Find Account (findAccount), List company accounts and optionally filter by email domain or external ID. Classification: read.
  • Find Contact (findContact), Look up a contact by handle (email, phone, etc.) or other identifying field. Classification: read.
  • Find Conversation (findConversation), Find a conversation by search filters such as subject, participants, tags, inbox, etc. Classification: read.
  • Remove Contact Handle (removeContactHandle), Remove a handle (email, phone number, etc.) from an existing Contact. Classification: read.
  • Remove Conversation Links (removeConversationLinks), Remove external links from a conversation in Front. Classification: read.
  • Send Message (sendMessage), Send a new message (starts a conversation) with subject, recipients, body, attachments, tags, etc. Classification: read.
  • Send Reply (sendReply), Send a reply to a conversation in Front. Classification: read.
  • Update Account (updateAccount), Update an existing account in Front. Classification: read.
  • Update Contact (updateContact), Update an existing contact in Front. Classification: read.
  • Update Conversation (updateConversation), Modify conversation properties: status, assignee, inbox, tags, etc. Classification: read.
  • Update Link (updateLink), Update the name or external URL of a Link in Front. Classification: read.

Trigger contracts

  • New Comment, polling.
  • New Inbound Message, polling.
  • New Outbound Message, polling.
  • New Tag Added to Message, polling.
  • New Conversation State Change, polling.

Verification

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

Capability summary

Authenticationcustom
Supported objects26
Supported actionsNot published
Triggers5

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Front API Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Comment Yes No Add a comment (internal note) to a conversation in Front.
Add Contact Handle Yes No Add a handle (email, phone number, etc.) to an existing Contact.
Add Conversation Links Yes No Link external references (URLs) to a conversation.
Add Conversation Tags Yes No Add one or more tags to a conversation.
Assign/Unassign Conversation Yes No Assign a conversation to a teammate or remove assignment.
Create Account Yes No Create a new account in Front.
Create Contact Yes No Create a new contact in Front.
Create Draft Yes No Create a draft message in Front.
Create Draft Reply Yes No Create a draft reply to an existing conversation (subject/quote etc.) without sending immediately.
Create Link Yes No Create a Link in Front (name, external URL).
Find Account Yes No List company accounts and optionally filter by email domain or external ID.
Find Contact Yes No Look up a contact by handle (email, phone, etc.) or other identifying field.
Find Conversation Yes No Find a conversation by search filters such as subject, participants, tags, inbox, etc.
Remove Contact Handle Yes No Remove a handle (email, phone number, etc.) from an existing Contact.
Remove Conversation Links Yes No Remove external links from a conversation in Front.
Send Message Yes No Send a new message (starts a conversation) with subject, recipients, body, attachments, tags, etc.
Send Reply Yes No Send a reply to a conversation in Front.
Update Account Yes No Update an existing account in Front.
Update Contact Yes No Update an existing contact in Front.
Update Conversation Yes No Modify conversation properties: status, assignee, inbox, tags, etc.
Update Link Yes No Update the name or external URL of a Link in Front.
New Comment Yes No polling trigger declared by the pinned package.
New Inbound Message Yes No polling trigger declared by the pinned package.
New Outbound Message Yes No polling trigger declared by the pinned package.
New Tag Added to Message Yes No polling trigger declared by the pinned package.
New Conversation State Change Yes No polling trigger declared by the pinned package.

Triggers

New Comment · Poll

Fires when a new comment is posted on a conversation in Front.

Inputs

  • conversation_id · string
New Inbound Message · Poll

Fires when a new message is received in a shared inbox.

Inputs

  • inbox_id · string
New Outbound Message · Poll

Fires when a message is sent or replied to in Front.

Inputs

  • inbox_id · string
New Tag Added to Message · Poll

Fires when a tag is applied to a conversation.

Inputs

  • conversation_id · string
New Conversation State Change · Poll

Triggers when a conversation changes to a specified state.

Inputs

  • conversation_id · string
  • desired_state · string

Setup

Setup

  1. Add the Front 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-front@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 21 actions and 5 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 Front 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-front@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.