Automation Guide Template
[Workflow Name - Be Descriptive and Action-Oriented]
Section titled “[Workflow Name - Be Descriptive and Action-Oriented]”What You’ll Build
Section titled “What You’ll Build”By the end of this guide, your workflow will automatically:
- [Specific action 1]
- [Specific action 2]
- [Specific action 3]
- [End result]
Time to complete: [Realistic estimate, e.g., “15-20 minutes”]
Difficulty: [Beginner/Intermediate/Advanced]
Platform: [n8n/Zapier/Make.com]
[Add a screenshot of your completed workflow here]
Before You Start
Section titled “Before You Start”You’ll need:
- [Platform name] account ([Link to sign up - mention free tier if available])
- [Service 1] account (e.g., Gmail)
- [Service 2] API key (e.g., OpenAI - [link to get API key])
- [Optional tool or account]
Cost estimate: [e.g., “Free tier works fine. OpenAI costs ~$0.10 per 100 emails processed”]
How It Works
Section titled “How It Works”The workflow in plain English:
- [Platform] checks for [trigger event, e.g., “new email”]
- It sends the [data] to [AI service]
- The AI [does something, e.g., “classifies the email”]
- Based on the result, it [takes action, e.g., “applies a label”]
- Finally, it [optional step, e.g., “sends a Slack notification”]
Why this is useful: [Real-world benefit, e.g., “Save 2 hours per day on email triage”]
Step 1: Create a New Workflow
Section titled “Step 1: Create a New Workflow”- Log in to [platform name]
- Click “New Workflow” in the top right corner
- Give it a name:
[Suggested workflow name]
[Add screenshot showing where to click]
Step 2: Add the Trigger
Section titled “Step 2: Add the Trigger”What we’re doing: Setting up [what triggers the workflow]
- Click anywhere on the canvas to add your first node
- In the search box, type “[Trigger name]” (e.g., “Gmail Trigger”)
- Select “[Exact node name]” from the results
[Add screenshot with arrows pointing to UI elements]
Configure the Trigger
Section titled “Configure the Trigger”- Click “Sign in with [Service]” to connect your account
- In the Event dropdown, select “[Event type]” (e.g., “Message Received”)
- Set [Setting name] to “[Value]” (e.g., “Poll Times” to “Every 5 minutes”)
- Click “Execute Node” to test the connection
[Add screenshot of configuration panel]
What this does: [Explain in plain language what this trigger monitors and when it fires]
Troubleshooting:
- Can’t connect account? Make sure you’re logged into [Service] in another tab
- No test data appearing? Send yourself a test email and click “Execute Node” again
Step 3: Add [Next Node]
Section titled “Step 3: Add [Next Node]”What we’re doing: [Explain the purpose of this node]
- Click the + button on the right side of your trigger node
- Search for “[Node name]”
- Select “[Full node name]”
[Add screenshot showing the + button location]
Configure [Node Name]
Section titled “Configure [Node Name]”Fill in these fields:
| Field | Value | What it does |
|---|---|---|
| [Field 1] | [Value or variable] | [Explanation] |
| [Field 2] | [Value] | [Explanation] |
| [Field 3] | Click “Add Field” → Select “[Option]“ | [Explanation] |
Using data from previous steps:
To use the email subject from Step 2:
- Click in the [Field name] box
- Click the variable icon (looks like a tag)
- Navigate to: [Path to variable] → [Variable name]
- Select it to insert:
{{ $json.subject }}
[Add screenshot of variable picker]
Example configuration:
Prompt: Classify this email into one of these categories: Urgent, Important, Marketing, or Spam.
Email subject: {{ $json.subject }}Email body: {{ $json.body }}
Return only the category name.Test This Node
Section titled “Test This Node”- Click “Execute Node”
- You should see output like:
"Important"
[Add screenshot of successful test output]
Troubleshooting:
- Error: “Missing API key”? Check that you added your API key in Step 2
- Getting weird results? Make sure your prompt is clear and specific
Step 4: [Continue with Additional Steps]
Section titled “Step 4: [Continue with Additional Steps]”Step 5: Add Decision Logic (If/Else)
Section titled “Step 5: Add Decision Logic (If/Else)”What we’re doing: Taking different actions based on the AI’s classification
- Add an “IF” node after your [previous node]
- Click “Add Condition”
- Configure like this:
- Value 1:
{{ $json.category }}(from previous node) - Operation:
Equal - Value 2:
Urgent
- Value 1:
[Add screenshot of IF node configuration]
True Branch: Handle Urgent Emails
Section titled “True Branch: Handle Urgent Emails”If the condition is TRUE (email is Urgent):
- Click the “true” output and add a “[Action Node]” (e.g., “Gmail”)
- Configure the action:
- Operation: “Add Label”
- Label: “URGENT”
- Message ID:
{{ $json.messageId }}
False Branch: Handle Other Emails
Section titled “False Branch: Handle Other Emails”If the condition is FALSE:
- Click the “false” output and add a “[Different Action]”
- Configure for normal processing
[Add screenshot showing both branches]
Step 6: Activate Your Workflow
Section titled “Step 6: Activate Your Workflow”Almost done! Let’s turn it on.
- Click the toggle switch in the top right to “Active”
- The switch should turn green
[Add screenshot showing the active toggle]
What happens now: [Explain when the workflow runs and what triggers it]
Testing Your Workflow
Section titled “Testing Your Workflow”Manual Test
Section titled “Manual Test”- [Trigger action, e.g., “Send yourself a test email”]
- Wait [time interval]
- Check that [expected result happened]
Check Execution History
Section titled “Check Execution History”- Go to Executions in the left sidebar
- You should see your workflow runs
- Click on any execution to see details
[Add screenshot of execution history]
Green checkmark = Success! Red X = Error (click to see details)
Customizing Your Workflow
Section titled “Customizing Your Workflow”Ideas to make it better:
- Add more categories: Update your AI prompt with categories like “Newsletter”, “Meeting Request”
- Send notifications: Add a Slack or Discord node to alert you about urgent emails
- Add filtering: Use an IF node at the start to only process emails from specific senders
- Schedule reports: Add a Cron trigger to send a daily summary
Troubleshooting
Section titled “Troubleshooting”Workflow isn’t running
Section titled “Workflow isn’t running”Check:
- Is the workflow active? (Toggle in top right should be green)
- Is the trigger configured correctly? (Click “Execute Node” to test)
- Check execution history for errors
AI returning unexpected results
Section titled “AI returning unexpected results”Fix:
- Make your prompt more specific
- Add examples to the prompt: “For example: ‘Meeting tomorrow’ = Urgent”
- Test with the “Execute Node” button to iterate quickly
Node showing an error
Section titled “Node showing an error”Common fixes:
- Authentication errors: Reconnect your account in the credentials panel
- Missing data: Check that previous nodes ran successfully
- Rate limits: Add a delay between nodes or reduce polling frequency
Still stuck?
- Check [platform name]‘s [community forum link]
- Search their [documentation link]
- [Platform Discord/Slack if available]
What You’ve Learned
Section titled “What You’ve Learned”- ✅ How to set up a trigger in [platform]
- ✅ How to connect [service 1] and [service 2]
- ✅ How to use AI for [task]
- ✅ How to add conditional logic with IF nodes
- ✅ How to test and activate workflows
Download This Workflow
Section titled “Download This Workflow”Want to skip the setup? Download the complete workflow:
[Add link to your workflow export file here]
To import:
- Click “Import from File” in [platform]
- Select the downloaded file
- Update credentials with your API keys
- Activate!
Next Steps
Section titled “Next Steps”Build on this workflow:
- [Related workflow idea 1]
- [Related workflow idea 2]
Related guides:
- [Link to similar automation guide]
- [Link to related topic]
Join the community:
- [Platform] Community Forum
- [Platform] Discord
- [Share your workflow in the community]
Questions about this guide? Open a discussion
Found an issue? Report it here