How to Submit a Workflow

Sharing on the forum is the recommended way to get people to use your workflow and help you polish it by finding bugs and requesting features. Once a workflow is determined to be generally stable and trusted by a number of users, the Alfred team will invite you to submit it officially to the Alfred Gallery.

The strongest candidates follow the Style Guide, have keywords with three characters or more, allow for user configuration, and include icons which are at least 256×256px.

Which Workflows Are Included

Workflows in the Gallery can have a single function or perform a set of related tasks. They can use no code or be programmed in any language, and they can satisfy a niche or interconnect popular services.

Workflows must respect user privacy and be safe. They can rely on external software but should never download and run it themselves after being installed or bypass macOS safety features like Gatekeeper. If they contain compiled binaries, they must be signed and notarised. The Alfred community expects to be able to audit a workflow’s contents.

Preparing Your Workflow

Expressed as a list, to make your workflow ready for the Gallery (click each item to expand details):

• Do share it on the forum.

  Presenting the workflow on the forum helps to get users to gather feedback and general interest.
• Do write instructions which follow the Style Guide.

  Consistent instructions make it easier for users to understand and choose your workflow.
• Do use sensible keywords with several characters.

  Keywords which are too short can get lost amongst results or conflict with other workflows. While there are exceptions, workflow keywords (including in Script Filters, File Filters, or similar) should in general be at least three characters long. Ideally they will also be user-configurable.
• Do use an icon at least 256x256 px.

  A minimum main icon size of 256x256 px is required to guarantee image quality.
• Do not use an auto-updater.

  Workflows available in the Gallery are updatable from Alfred. Workflows must never update themselves to not cause conflicts.
• Do not download extra software.

  Every bit of executable code must be contained in the workflow. The workflow must never install extra software itself, including (but not limited to) running pip install, gem install, brew install, or curling a binary. Bundling libraries with the workflow is accepted. Homebrew dependencies must be handled by Alfred.
• Do not use unsigned and non-notarised binaries.

  Workflows must not have unsigned and non-notarised binaries, or otherwise try to bypass this macOS security feature (e.g. by removing quarantine). Scripts don’t fall into this category.