Cross-system ticket reporting
Support ops & back officeDaily schedule → pull tickets from ITSM and the engineering tracker plus the related docs, analyse, prioritise, publish a bottleneck report to Slack or email.
How the workflow runs
- Trigger
Daily schedule
Runs on a timer, not on someone remembering.
- </>
Pull from every system
Tickets from ServiceNow and Jira, plus the Confluence docs they reference.
ServiceNow
Confluence
Jira
- Logic
Analyse & prioritise
Find where work is actually stuck rather than listing everything open.
Bottleneck analysis agent -
Publish the bottleneck report
Land it in Slack or email where the people who can unblock it already are.
Slack
Also works with
CRM, data & ops
-
Salesforce
-
Gainsight
-
Slack
-
Microsoft Teams -
Asana
-
Linear
-
Airtable
-
Segment
-
Snowflake
-
Twilio
-
Shopify
Knowledge & content
-
SharePoint
-
Google Drive
-
Notion
-
Guru
-
Document360
-
Contentful
Ticketing & support
-
Zendesk
-
Freshdesk
-
Intercom
-
Salesforce Service Cloud
-
HubSpot
-
Front
-
Gorgias
-
Help Scout
-
Kustomer
-
Gladly
-
Zoho Desk
-
Dixa
-
Re:amaze
-
Jira Service Management
Or anything else you run. If it has a REST or GraphQL API, an MCP server, or a database we can reach, the workflow runs against it — however many systems one job needs.