> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firsttouch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Social Orchestration

> Profile views, connection requests, and messages within your flows.

In the **Flow Builder**, you can automate several Social Platform interactions inside your flows.

## Available Actions

<CardGroup cols={1}>
  <Card color="#3c5d29" icon="eye" title="View Profile">
    Visits the prospect's profile as a flow step.

    * **Delay support:** You can schedule this step with the same delay controls used in other flow actions.
    * **Best use:** Place it before conditional logic when you want fresher Social Platform context before later steps.
  </Card>

  <Card color="#3c5d29" icon="user-plus" title="Connection Request">
    Sends a connection request to the prospect.

    * **Acceptance window:** You can define how long First Touch should wait for the request to be accepted.
    * **Auto-withdraw:** You can automatically withdraw unaccepted requests after the configured wait period.
    * **Personalized note:** You can optionally include a note up to **300 characters**.
    * **Approval mode:** You can require team approval before the request is sent.
  </Card>

  <Card color="#3c5d29" icon="comment-dots" title="Send Message">
    Sends a Social Platform message to an existing 1st-degree connection.

    * **Connection rule:** This step can only be used after a successful connection path or when the contact is already connected.
    * **Approval mode:** You can require team approval before sending.
    * **Reply tracking:** You can configure how long the flow should keep tracking replies.
    * **Preview:** You can test the generated message against a sample contact before publishing.
  </Card>
</CardGroup>

<Note>
  InMail is coming soon. Do not plan on InMail in a flow unless it is explicitly enabled for your workspace.
</Note>

## Builder Rules

* Each branch can contain only **one** connection request step.
* Social Platform messages are limited to **5 messages per branch**.
* Connection requests cannot be added inside an **Accepted** branch.
* Social Platform messages can only be used where the contact is already connected or becomes connected through the flow.