Connect Pylon so Coworker can reason about customer support activity. Pylon is admin-connected with one organization API token — there is no per-user connect flow.
What Coworker can do with Pylon
Index support issues and their full conversations (including internal notes), customer accounts and contacts, your team roster and teams, the custom-field schema, and help-centre knowledge base articles
Produce one account-health digest per customer whose issues moved in the window: what they raised, what got resolved, where the ball is sitting (waiting on us versus waiting on them), what is aging in the open backlog, and how they scored you on CSAT or NPS. Quiet accounts produce nothing.
Answer support questions on demand — what is still waiting on us for a given account this week, a summary of one issue and what the customer was told, or whether a help-centre article exists on a topic
Issues become Task entities under the team that owns them, customer accounts become Customer entities, and teammates and contacts become Person entities that merge with the same humans from HubSpot, Salesforce, Zendesk or Slack. Message threads, survey answers, statuses, tags and ticket forms stay in the raw store and power the reports.
Before you start
You must be a Coworker Network Admin
You need a Pylon organization API token, minted at Settings > API Tokens in Pylon. Only a Pylon admin can create one.
Connect as an admin
Open Data Sources from the admin settings in Coworker and select Pylon.
Paste the organization API token.
Save. The token's identity is used to verify the organization and deduplicate credentials.
Connect as a member
Pylon has no per-user connection. One admin token covers the whole workspace, and access is governed by the Pylon access policy described below.
Good to know
All indexed Pylon content sits behind a single private access policy whose members are your active Pylon users. Deactivated teammates drop out on the next sync while their history stays intact, and customer contacts are never members. Nothing Pylon is workspace-public.
Anything Coworker writes back to Pylon is attributed to the API token's identity, not to the person who asked for it.
Pylon does not expose custom-role issue filters over its API, so a teammate on a filtered custom role may see slightly more in Coworker than in Pylon. The difference is bounded to support staff and never reaches anyone outside the policy.
Knowledge base articles stay inside the same private policy even when your help centre is public. Published articles are indexed for search; drafts are not.
Issue states are workspace-specific. Beyond Pylon's base states, your workspace may define custom status slugs.