Document a complex branching automation for team handoff

Create clean operational documentation for a multi-step automation so colleagues can maintain it without you.

You getAutomation Overview, branching Architecture Map and connected Services and Dependencies

Prompt

Prompt
Act as a technical documentation specialist. Turn the multi-branch workflow details below into a standard operating document for team handover.
- Summarize the business purpose, owners, and trigger criteria in non-technical terms.
- Map every branch path, noting the specific condition that routes data into it.
- List each external account, connection, and webhook by name and purpose. Never write out passwords, tokens, or keys; note only where they are stored.
- Provide an operational troubleshooting guide for when steps stall.
- Write 'Not provided' for any missing detail instead of guessing.
Output format:
1. Automation Overview (Purpose, Systems, Trigger, Maintainer)
2. Branching Architecture Map (nested list of paths, conditions, and actions)
3. Connected Services and Dependencies (table with Service Name, Auth Method, Permissions Needed)
4. Maintenance and Failure Runbook (common bugs, check locations, manual recovery)

Here are the workflow steps, routing rules, and tools:

Example output

Example for: an enterprise onboarding workflow routing accounts by contract size and geography

  1. Automation Overview
  • Purpose: Automatically routes newly signed customers to the correct regional onboarding team and sets up shared project spaces.
  • Systems: DocuSign, Salesforce, Asana, Slack, Google Drive.
  • Trigger: DocuSign envelope status changes to 'Completed'.
  • Primary Maintainer: RevOps Systems Administrator.
  1. Branching Architecture Map
  • Trigger: DocuSign envelope signed and completed.

    • Branch A: Contract Value greater than or equal to $50,000 (Enterprise Tier)

      • Condition: Opportunity Amount >= 50,000 in Salesforce.
      • Action 1: Create Asana project from Enterprise Onboarding Template.
      • Action 2: Generate dedicated Google Drive customer folder with restricted access.
      • Action 3: Post alert to #enterprise-wins Slack channel mentioning the dedicated CSM.
    • Branch B: Contract Value under $50,000 (Commercial Tier)

      • Condition: Opportunity Amount < 50,000 in Salesforce.
      • Action 1: Create shared Asana task in the pooled Onboarding Board.
      • Action 2: Trigger automated email sequence via marketing automation.
    • Branch C: Missing Account Data (Fallback Exception)

      • Condition: Opportunity record lacks Region or CSM assignment.
      • Action 1: Route task to Deal Desk queue in Salesforce for manual enrichment.
  1. Connected Services and Dependencies
Service NameAuth MethodPermissions Needed
DocuSignOAuth 2.0 Service UserRead Envelope Status, Read Documents
SalesforceIntegration User API ProfileRead/Write Opportunities, Accounts, Tasks
AsanaAdmin Personal Access TokenCreate Projects, Modify Project Templates
SlackWorkspace Bot TokenPost to Public Channels, Mention Users
  1. Maintenance and Failure Runbook
  • Check point: If Branch A fails to generate an Asana project, check whether the Enterprise Template ID was modified or archived in Asana.
  • Recovery: Re-trigger the webhook by using the manual 'Resend Webhook' button on the DocuSign envelope history page.
Written by AI from this prompt. Your results will vary.

Paste your automation trigger, paths, branch conditions, and connected apps after the prompt into ChatGPT, Claude, or Gemini. Do not paste passwords, API tokens, or keys; name the app and where the credential is stored instead. Check the finished document against your live automation before sharing it.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Automation & Workflows