Submit your template for built-in consideration

Prerequisites

• The source entry is under My Templates; Suggest is disabled for built-in and Team entries.
• The template main file still exists and TemplateLibrary can resolve its path safely.
• Internet access to the HTTPS submission endpoint.
• Complete metadata and a README are recommended; without a README, the service creates a fallback from title and description.

Supported modes

• Desktop Mode — A personal template can be submitted while Studio is in Desktop Mode. The packaged Recommended mode can be window, chrome_cdp, or mixed and is not rewritten from the active workspace at submission time.
• Browser Mode — The submission flow also works in Browser Mode and needs no active Chrome/CDP connection; it sends the saved template file rather than executing the workflow during submission.

What it does

Suggest as Built-in packages one My Template entry into a temporary ZIP and sends it to the RunMacro submission endpoint. The archive contains the macro as template.pmacro-template, plus submission.json, SUBMISSION_INFO.txt, and a README. Template metadata, app version, creation time, and the Sender, Contact, and Notes fields are included in an HTTPS POST. An ok: true response confirms receipt for consideration; it does not automatically turn the entry into a built-in template.

When to use it

• You have a general, tested workflow or block that could help many other users.
• The template has enough metadata, instructions, and sample data for a reviewer to understand it independently.
• You want to submit a built-in candidate through the integrated flow instead of assembling a ZIP manually.
• You need to include contact details or implementation notes for the reviewer.

When not to use it

• The template is intended only for a private team — use Upload Team instead.
• The workflow still contains real accounts, tokens, cookies, personal paths, or confidential data.
• The template has not been tested, has missing dependencies, or uses commands unavailable in the current build.
• You need immediate publication or in-app review tracking; this flow only submits an intake package.

Configuration steps

1. Test the workflow or block in its intended mode and remove all real data from its commands.
2. Choose File › Save current macro as template...; set name, ID, description, Category, Tags, Recommended mode, Full/Block, Version, icon, and README/notes.
3. Open File › Open macro template... and expand My Templates.
4. Select the intended entry and inspect its details, command list, and dependencies. Use Edit or save again if metadata needs correction.
5. Click Suggest, the action whose tooltip says the template will be suggested as built-in.
6. Enter Sender, Contact, and Notes. All three may be blank, but clear information makes review easier.
7. Press OK. RunMacro creates a temporary ZIP containing the macro, metadata JSON, information text, and README, then sends it to the endpoint.
8. Wait for the result. Template suggestion sent successfully means the server returned ok: true.
9. If submission fails, read the error and note the ZIP path shown in the message; fix the network or content, then reopen Suggest to send a new package.

Every option explained

Expected result

RunMacro creates template_submission__<id>__<timestamp>.zip in a temporary folder and POSTs its Base64 content with metadata. When the endpoint returns ok: true, the app reports success. This is a submission receipt; the local entry remains under My Templates and has not become built-in.

Real example

Limitations and failure cases

• Only entries under My Templates can be suggested; the button is disabled for built-in and Team templates.
• A success message confirms endpoint receipt only, not approval, publication, or inclusion in a future release.
• RunMacro provides no submission list, review status, withdrawal action, or discussion history in the interface.
• Sender, Contact, and Notes are optional and format is not validated; missing information can make follow-up harder.
• The flow depends on the built-in endpoint and Internet access; HTTP failures show a status code, while non-JSON responses may be reduced to a short text excerpt.
• The ZIP includes only the main macro package, metadata, and README. External files or referenced PMacro children that were not embedded are not collected separately for submission.
• Suggest does not test-run the workflow or require a dependency check before sending; the submitter remains responsible for quality and run readiness.
• Temporary ZIP files are not automatically removed after success or failure, so the temp folder can accumulate packages.
• The Suggest dialog edits only the three sender fields; title, ID, mode, version, tags, and README must be corrected on the template beforehand.
• The UI has no step to preview the ZIP contents or POST payload before pressing OK.

Tips & common mistakes

Verification details

• core/template_submission.py
• ui/main_window.py
• core/template_library.py
• storage/json_store.py

Related commands