Daily Pylon support digest in Slack and email
Every weekday at 9am, post a clean Pylon support digest to Slack and email it to CS leadership so the team starts the day on the same page.
Integrations
Pylon
Slack
Gmail
Type
Categories
- Customer Support
- Operations
Build me a deterministic code workflow that sends a daily Pylon support digest to Slack and email. Trigger: cron, every weekday at 9:00am in the team's timezone (ask me which timezone).
Each run, call Pylon List Issues with an explicit start_time and end_time covering the trailing 24 hours. On Mondays, widen the window to cover Friday 9:00am through Monday 9:00am so the weekend is included. Keep the window under 30 days at all times because the List Issues endpoint is windowed.
From the returned issues, compute: counts bucketed by state (new, in-progress, awaiting-customer, resolved); counts grouped by team_id and by assignee_user_id from the issue payload; the count of items flagged SLA-at-risk; and the top 10 accounts by issue volume. For the top accounts, call Pylon Search Accounts to enrich account_id values into human-readable account names.
Format the digest as a single Markdown message: a short metric strip on top (new opened, closed, still open, oldest unresolved with age in hours), then a table with rows per status and columns for team or assignee, then the top 10 accounts table. Truncate the accounts list at 10 rows and append a link to a saved Pylon view for the rest. Keep the whole thing short enough to fit in one Slack message.
Dispatch the digest two ways. First, use Slack Send a Message to post to a channel I will configure. Second, use Gmail Send a Message to email the same Markdown content (rendered as plain text or simple HTML) to a CS leadership distribution list I will provide. Both sends should use the identical body.
No reasoning or LLM steps anywhere. Every node is a deterministic list, format, or dispatch operation. Ask me up front for: timezone, Slack channel, email recipients, the saved Pylon view URL, and whether to group by team or assignee in the main table.
What it does
- Pulls the last 24 hours of Pylon issues every weekday morning, with Mondays automatically covering the weekend.
- Buckets issues by status and team or assignee so you can see who is carrying what before standup.
- Surfaces the top accounts by issue volume and flags anything at risk of breaking SLA.
- Posts a fixed Markdown summary to a Slack channel and emails the same digest to a CS leadership distribution list.
What you’ll need
- A Pylon account with admin access so an API token can be created.
- A Slack workspace and a channel where the digest should land.
- A Gmail account that can send to your CS leadership distribution list.
How to customize it
- Change the schedule, the timezone, or the lookback window if you want an end-of-day or every-few-hours version.
- Swap the Slack channel and the email recipients, or send only to Slack and skip email.
- Adjust which fields appear in the digest, like grouping by team instead of assignee or hiding the top accounts section.
Use cases
- Daily Digests
- Notifications & Alerts
- Email Automation
