No native Intercom connector or live reply workflow is available in the current Threetone catalog. This guide prepares the authorization and action design.
Prepare the support workflow
Have a workspace administrator, a test conversation, and an owner for your integration’s OAuth lifecycle.2
Limit retrieved context
Bind the workspace and conversation ID before reading. Return relevant message excerpts and status, with only the contact fields needed for support. Avoid copying an entire contact profile or unrelated conversation history into a prompt.
3
Confirm audience and sender
Before a future write, show the destination conversation, sender identity, text, and whether the action is an internal note or customer-visible reply. On timeout, inspect the conversation before retrying. An accepted request must not be described as a delivered reply without matching evidence.
Frequently asked questions
Can a stored bearer token implement OAuth consent?
Can a stored bearer token implement OAuth consent?
No. Token storage and user authorization are different responsibilities. Your approved integration must manage consent, token lifecycle, and revocation.
Should a failed lookup create a new conversation?
Should a failed lookup create a new conversation?
No. Report the failed lookup and resolve its access or identifier problem. Creating a conversation is a separate action with a reviewed recipient.