Skip to content

The Channels page shows each email sender's integration id with a copy button #107

Description

@Silthus

Part of #68. Asked by Michael on 2026-09-22.

What to build

On the workflows Channels page, every configured email sender shows its integration id with a copy button, so a person writing a workflow in code can paste it into from: { integrationIds: [<id>] } without opening the browser's developer tools or the API.

  • The id sits beside the sender in the list row, as plain text with a copy control (CopyToClipboardInline from lib/components/CopyToClipboard), never as an editable field.
  • The tooltip or helper text says what the id is for in one short line, sentence case, no jargon: for example "Integration id. Use it as integrationIds in a workflow defined in code."
  • Same treatment for the other channel types on that page only if they share one row component and it costs nothing; otherwise email only.
  • Nothing else on the page changes.

Start at products/workflows/frontend/Channels/MessageChannels.tsx and follow it to the component that renders the rows (it may be a shared integrations list under frontend/src/scenes/settings/; if so, add the id there behind a prop so other settings pages do not change).

Write scope

  • products/workflows/frontend/Channels/**
  • The shared row component the page uses, if the id has to live there, behind a prop
  • One story for the row with the id, in the same directory

Proof gate

  • A Storybook story renders the row with the id and the copy control, screenshot before and after on the PR, at 1440px and at 520px
  • pnpm --filter=@posthog/frontend typescript:check passes
  • The existing Channels tests, if any, pass
  • hogli ci:preflight --strict on push

Blocked by

Nothing.

Stack base and ship target

  • Branch feat/workflows-channel-integration-id cut from upstream/master.
  • A draft PR against upstream PostHog/posthog, --head Silthus:feat/workflows-channel-integration-id. It stays a draft until Michael says otherwise. Nothing merges into the fork's master.
  • Invoke writing-ui-components, writing-user-facing-copy, writing-tests, reviewing-with-coderabbit and writing-pr-descriptions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions