PostHog / PostHog/posthog

Native "Send reply" action in workflow builder for Support conversations

Open
#60,282 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Feature request

The workflow automation docs cover ticket management actions (status changes, SLA, assignment) but there's no native action for posting a reply into a conversation. This is a critical missing piece for AI-assisted support workflows.

Use case:

  1. Trigger on $conversation_message_received
  2. Call an external LLM via webhook to generate a draft reply
  3. Post that reply back into the conversation

Step 3 currently has no supported path – the /compose/ endpoint blocks external API access (see related bug report), and there's no native workflow action for sending replies.

Proposed solution:

Add a native "Send reply" action under the Support section in the workflow builder, which accepts:

content – the message body (supports output variable references like {variables.draft_reply})
conversation – the ticket ID (can be pulled from {event.properties.ticket_id})
Optionally:

is_private – boolean to post as an internal note vs. customer-visible reply
Why this matters:

This closes the loop for AI-assisted support workflows entirely within PostHog, without requiring external API access or workarounds. The trigger, LLM call, and reply can all be orchestrated natively.

Debug info
N/A

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the workflow automation docs and the existing /compose/ endpoint behavior described in the issue. Trace how a conversation message trigger, webhook output variable, and ticket ID are represented, then define completion as a Support workflow action that posts content to the selected conversation with the optional private-note setting.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design, full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.