Publishing Guide

Clear name — action-oriented, under 60 characters. "WhatsApp Auto-Reply When Busy" is better than "My Task 1".

Specific description — explain what the task does, when it triggers, and what it needs. Users should know exactly what they're installing.

Proper category — pick the most specific category that fits. "Communication" for messaging automations, "Productivity" for workflow tasks.

Relevant tags — add up to 5 tags that help users discover your task. Be specific: "whatsapp", "auto-reply", "busy" is better than "automation".

All new tasks go through review before being published on the marketplace.

Admin reviews within 24 hours of submission. Three possible outcomes:

Approved — your task goes live on the marketplace immediately.

Changes Requested — you'll receive feedback with specific changes. Edit and resubmit from your dashboard.

Rejected — with a detailed explanation. Common reasons include duplicate tasks, misleading descriptions, or policy violations.

After 3 approved tasks with 0 rejections, you earn Trusted Developer status and your future tasks publish instantly.

uses-ai — Task uses AI to make decisions at runtime.

uses-web — Task reads web content (scraping, fetching data).

uses-web-form — Task submits web forms on behalf of the user.

uses-web-session — Task accesses logged-in web pages. Requires explicit user approval at install time.

uses-connectors:slack, uses-connectors:email, etc. — Task sends data to external services.

These tags are auto-generated from your task definition. They help users understand what permissions your task needs.

Duplicate of an existing task already on the marketplace.

Description doesn't match what the task actually does.

Task requests permissions it doesn't need for its stated function.

Task definition contains errors or won't execute correctly.

Offensive, harmful, or spammy content.

Write a description that explains the user benefit, not the technical mechanism. "Never miss an important email" beats "Monitors IMAP inbox and sends push notifications".

Choose the most specific category — users browse by category.

Include capability tags honestly — trust builds installs.

Respond to reviews — engaged developers build loyal user bases.

Iterate based on feedback — update your task when users suggest improvements.