Publishing Your Own Templates

Any automation you've built can become a reusable template — for reuse inside your tenant, or for the community marketplace (after a StackJack review). The flow is: save the automation as a template → edit the draft → run the safety scan → submit for marketplace review.

Save an automation as a template

1. Open the automation's detail page and click Save as template in the header.
2. Enter a Slug — lowercase letters, digits, and hyphens (it is lowercased for you on submit). The slug must be unique; a conflict is reported as SJ-TEMPLATE-SAVE-CONFLICT.
3. Pick a Category (defaults to "General").
4. Click Save as template. You land on the new template's detail page.

What is never copied. Saving as a template sanitizes the automation automatically: webhook secrets, tenant IDs, Anthropic IDs, notification emails, consent state, and run data are never copied into the template. The result starts as a Private draft. Templates belong to your tenant: the draft appears in your own tenant's template gallery (your teammates can see, edit, and install it too), but no other tenant can see it unless it is published to the marketplace.

Edit the template draft

From your template's detail page, click Edit draft (available to the owning tenant only — curated built-in templates are managed by StackJack). The editor covers:

• Identity — display name (required), summary, category, and long description.
• Prompts — the system prompt template and description template. Use {{parameter_name}} placeholders anywhere you want the installer to supply a value.
• Tools — required and recommended tool names, one per line (duplicates are removed on save).
• Trigger and payload — the trigger type the installed automation will use (on demand, scheduled with a default cron, or webhook), and for webhooks the payload mode. Note the inline warning: a template whose payload mode passes the full webhook body verbatim cannot be submitted to the marketplace — full-payload passthrough is limited to templates you keep private.
• Notes — setup notes and support notes shown to installers.

Finish with Save draft (returns to the detail page) or Save and go to publish (continues straight to the publish review).

Publish review: visibility and the safety scan

Open Publish review from the template detail page.

1. Choose the Target visibility the scan should test against:
   • Private — not published; visible inside your tenant only.
   • Tenant-shared — visible to everyone in your tenant.
   • Marketplace — submitted to StackJack for review and, if approved, published to all tenants.
2. Click Run scan. The scan produces two report cards:
   • Policy checks — marketplace rules applied to your manifest. Each violation shows a code, a Blocked or Warn severity, and a hint for fixing it.
   • Content findings — an automated scanner that looks for personal data and secret-like strings in your template's text. Each finding shows the category, severity, the field it was found in, a redacted preview, and a hint.
3. For the Marketplace target, click Submit for marketplace review. The button stays disabled while the report contains any Blocked items — fix them via Edit draft, then re-run the scan. After submitting, your template's detail page shows a "Pending marketplace review" banner until StackJack approves or rejects it.

Submitting to the marketplace is currently the only action that changes a template's visibility. The Private and Tenant-shared choices scope the safety scan, but the publish review page has no apply action for them — your template remains a Private draft until it is submitted to and approved for the marketplace. In practice this costs you nothing: because templates belong to your tenant, a Private draft is already visible to your teammates in your tenant's template gallery. Marketplace publication is what makes it visible to other tenants.

After you submit to the marketplace

• Approved — your template becomes visible in the gallery as a Community template.
• Rejected — your template's detail page shows the reviewer's rejection reason (SJ-TEMPLATE-REJECTED). Edit the draft to address it and resubmit through the same publish review flow.

Errors you may see