Template Guidelines Summary
- - Focus on practical automations with clear trigger, action, and business outcome.
- - Use concise, grammatically correct English and Markdown formatting.
- - Avoid HTML tags, vague titles, duplicate templates, and copied marketplace content.
- - Never expose private app credentials, webhook URLs, user IDs, or customer data.
Template Quality
- Clear purpose: Solve one recognizable business problem and make the expected outcome obvious.
- Production ready: Test with realistic data, document required accounts, and include recovery paths for failures.
- No secrets: Never ship API keys, passwords, bearer tokens, private URLs, customer data, or environment-specific IDs.
- Original work: Submit only original templates or properly licensed open-source work with attribution.
- Naming: Name the Zap by the trigger and outcome, not by internal implementation details.
- Setup clarity: Call out which fields users must map and which fields are optional.
Description Copy
- Start with the real workflow outcome in the first sentence.
- Use short H2 sections for How it works, Requirements, Setup, and Customization.
- Use examples from sales, support, marketing, finance, or operations when relevant.