LinkedIn Message Unipile Auto-Response Workflow

# LinkedIn Message Unipile Auto-Response Workflow

---
name: workflow-unipile-linkedin-message-response
description: "Process Unipile LinkedIn message webhooks, deduplicate replies, analyze follower count, draft non-commitment response, auto-reply via Unipile API, and send email notification."
type: workflow
execution: stateful
inputs:
  - name: webhook_payload
    type: object
    source: user
    label: "Unipile Webhook Payload"
    field: textarea
    required: true
    placeholder: '{"event": "message_received", "message_id": "msg_XXXXXXXX", "chat_id": "chat_XXXXXXXX", "account_id": "{{UNIPILE_ACCOUNT_ID}}", "sender": {"name": "Jane Doe", "profile_url": "https://linkedin.com/in/janedoe", "followers_count": 15400}, "message": "what time works best"}'
    help: "Inbound JSON webhook payload from Unipile containing message_id, chat_id, account_id, message, and sender details"
  - name: unipile_dsn
    type: string
    source: user
    label: "Unipile DSN"
    required: false
    placeholder: "apiXX.unipile.com:PORT"
    help: "Unipile API server host and port (from your Unipile dashboard). Only needed for the direct-API fallback; not required when using the DeepVista MCP send_linkedin_message tool."
  - name: unipile_api_key
    type: string
    source: secret
    label: "Unipile API Key"
    required: false
    help: "Unipile X-API-KEY. Only needed for the direct-API fallback (DeepVista MCP handles credentials server-side). Store as a secret / environment variable (UNIPILE_API_KEY) — never hardcode in this skill."
  - name: unipile_account_id
    type: string
    source: user
    label: "Unipile Account ID"
    required: false
    placeholder: "acct_XXXXXXXX"
    help: "The Unipile account ID of the LinkedIn account this workflow monitors. If unset, resolve it via DeepVista MCP: search context cards for 'LinkedIn account connected', or run the create_linkedin_auth_link setup flow (see Setup & Prerequisites)."
  - name: recipient_email
    type: string
    source: user
    label: "Notification Recipient Email"
    field: email
    required: true
    placeholder: "user@example.com"
    help: "Email address where the confirmation, auto-sent reply, follower count, and thread link will be sent"
---

## Setup & Prerequisites (via DeepVista MCP)

Before running the workflow, verify all requirements are satisfied. If anything is
missing, use the DeepVista MCP tools to complete the setup **conversationally** —
walk the user through it in chat rather than telling them to leave and configure
things manually.

### Requirement checklist

| Requirement | How to check | How to fix via MCP |
|---|---|---|
| LinkedIn account connected to Unipile | `search_context_cards` for a card titled "LinkedIn account connected" (tags: `LinkedIn`, `Unipile`) containing `unipile_account_id` | Call `create_linkedin_auth_link` and guide the user through it (see below) |
| `unipile_account_id` | Read it from the same context card | Filled automatically once the auth flow completes |
| `unipile_dsn` / `unipile_api_key` | Only needed for the raw-curl path (Step 5 fallback); not needed when using MCP tools | Prefer the MCP `send_linkedin_message` tool, which handles credentials server-side — never ask the user to paste an API key into chat |
| Notification email | Confirm `recipient_email` with the user | `send_notification_email` needs no setup; `send_email` requires the user's connected Gmail account |

### Connecting LinkedIn through chat

If no LinkedIn account is connected yet:

1. Call the DeepVista MCP tool `create_linkedin_auth_link` (optionally passing a
   `success_redirect_url`). It returns a Unipile **hosted auth URL**.
2. Show the URL to the user and ask them to open it in a browser and sign in to
   LinkedIn. The connection completes out-of-band — DeepVista is notified via the
   `account.connected` webhook, which records the new `unipile_account_id` in a
   context card ("LinkedIn account connected") tied to the user.
3. After the user says they've finished, re-run `search_context_cards` for the
   connection card to pick up `unipile_account_id`. If it hasn't appeared yet,
   wait briefly and retry, or ask the user to confirm the browser flow succeeded.
4. Never guess or fabricate an `account_id` — only use one recorded by the webhook
   or explicitly provided by the user.

### Preferred send path

When the DeepVista MCP `send_linkedin_message` tool is available, use it instead of
the raw Unipile curl in Step 5 — it sends from the user's connected account using
server-side credentials (`account_id`, recipient provider id, message text) and
returns `chat_id` / `message_id` for the notification step. Fall back to the direct
Unipile API only when the MCP server is unavailable and the user has supplied
`unipile_dsn` + `unipile_api_key` as secrets.

## Workflow

```mermaid
flowchart TD
  Input["Input"]:::dvTodo
  A["1. Receive & Parse Unipile Webhook"]:::dvTodo
  subgraph rowB [ ]
    direction TB
    B["2. Check Reply Status & Deduplicate"]:::dvTodo
    noteB["Terminated: self-sent message (is_sender: true)"]:::dvNote
  end
  C["3. Analyze Message, Profile & Follower Count"]:::dvTodo
  D["4. Draft Response (No Scheduling/Times)"]:::dvTodo
  E["5. Post Reply into Existing Chat Thread"]:::dvTodo
  F["6. Send Confirmation Email & Notify"]:::dvTodo
  Output["Output"]:::dvTodo
  Input e0@--> A
  A e1@--> B
  B e2@--> C
  C e3@--> D
  D e4@--> E
  E e5@--> F
  F e6@--> Output
  e0@{ animation: slow }
  e1@{ animation: slow }
  e2@{ animation: slow }
  e3@{ animation: slow }
  e4@{ animation: slow }
  e5@{ animation: slow }
  e6@{ animation: slow }