Tines story documentation enforcer and quality auditor
Build a workflow that audits documentation quality across all the automation stories/workflows in a tenant, then nudges the people responsible to improve the weak ones. Trigger it manually as a single run (add a schedule later if you want it recurring). Step 1 — Audit: Using the Tines connector (or your automation platform's API), scan every team/workspace the connector can reach and evaluate each story's documentation quality. Flag any story that looks under-documented — e.g. a default or auto-generated name, a missing or very short description, no explanatory notes on the canvas, no actions built at all, or actions that mostly still carry their default names. Output a JSON list of the flagged stories grouped by team, including enough identity (team, story name/id) and the specific issues found for each. Step 2 — Notify: Downstream of the audit, group the flagged stories by the person responsible — the story's owner, falling back to its creator when there's no owner — and email each person the list of stories they need to document. Send via SendGrid (or your team's email/notification tool — Slack, MS Teams, etc. would work just as well). Include a dry-run mode that composes and logs every message without actually sending, on by default so it's safe to test, and only sends real messages when explicitly enabled. Emit a summary of who would be (or was) notified and how many stories couldn't be attributed to anyone. Tools used: Tines, SendGrid
What this prompt builds
This workflow audits documentation quality across all Tines stories in a tenant, flags under-documented workflows based on missing descriptions, default names, and sparse notes, then emails each story owner a personalized list of their stories that need better documentation. It includes a dry-run mode for safe testing and helps teams maintain readable automation libraries for easier troubleshooting and onboarding.
The problem
Automation teams struggle when Tines builders ship stories without documentation — missing descriptions, default names, and no explanatory notes make sharing work difficult, troubleshooting costly, and onboarding new team members slow. This workflow audits every Tines story in the tenant, flags the under-documented ones based on quality signals like auto-generated names and sparse notes, then emails each story owner a personalized list of what needs fixing. It includes a dry-run mode for safe testing and helps teams maintain a readable automation library that cuts onboarding time and speeds up future changes.
Solution and impact
The workflow scans all accessible Tines stories, identifies documentation gaps, and delivers actionable nudges directly to the people responsible, making it easy for teams to improve their automation hygiene without manual tracking. By enforcing consistent documentation standards, it significantly reduces the time spent troubleshooting existing stories and onboarding new engineers who need to understand the automation estate. Teams gain a repeatable, low-friction way to maintain quality across their Tines tenant as it scales.