Publishing your agent

Publish a workflow as an agent, list it in the Agent Store, and follow its review and listing status.

Publishing turns a workflow into an agent: a packaged version that runs from My Agents with a simple form and can be added to other workflows as an agent flow. You can keep the agent to yourself, or list it in the Agent Store so Users can install it and you earn credits. See also Pricing & earnings and the Builder Dashboard.

Before you publish

  • All the workflow's neurons must form one connected flow, with no neuron left on its own.
  • The flow can't have a loop: circular workflows can't be published as agents.
  • Test the flow well: Users run it with their own inputs. See Running.
  • Decide what Users see of each input. In each GET input, under People using the agent, choose Can change (Users fill it in), Can see (Users see your value but can't change it) or Hidden (Users don't see it; your saved value is used).
  • In Memory › Settings, turn on Ships with the agent for each memory that should ship, and choose what a User's copy may learn. See Memory.

If something stops the workflow being published, the Publish button is greyed out. Hover over it to see why, for example "Multiple separate flows detected - connect all neurons into a single flow to publish".

Publish as an agent

  1. Click Publish in the canvas's top bar. The Publish as Agent dialog opens.
  2. Read What happens when you publish: the workflow becomes read-only, the agent is available to you in the Agent Store and My Agents, and other workflows can use it as an agent flow.
  3. Check Input visibility for agent users: each input shows Exposed, Visible (read-only) or Fixed, from your choices in GET.
  4. Check Required connections: the apps the agent acts in. Users connect their own accounts for these apps; yours are never shared. Users also see what your agent can change or delete in their accounts, from your Steps and AI actions, with delete actions marked Deletes data. The list comes from the version you publish, so publish again to refresh it.
  5. On the new canvas, if the workflow has Code neurons that read secrets, the dialog has a Secrets box. Choose there who provides each one: Mine (your value is used for every User's run, and a User can replace it with their own) or User provides (each User adds their own value before running the agent). Nothing is chosen for you, and publishing waits until every secret has an answer; it asks again when you publish an update. Not in your Secrets yet means you haven't added that secret on your Secrets page. Users never see a secret's value, your code or its logs.
  6. Click Publish Agent.

The dialog says Agent Published!. The agent is private: only you can use it. To list it in the store, click Publish to Community Store.

List it in the Agent Store

  1. Click Publish to Community Store after publishing, or open the listing button in the top bar (Published) and choose Publish to Agent Store.
  2. In the Publish to Agent Store dialog, fill in how the agent appears in the store:
    • a logo and the Agent name shown in the store (it can be different from the workflow name),
    • a short tagline and a Category,
    • a headline image,
    • About this Agent: what it does, how it works and who it's for,
    • Key Features and Tags.
  3. Under Pricing, set a One-Time Price and a Per-Run Royalty. Leave both at 0 for a free agent. See Pricing & earnings.
  4. Check the memory note: how many memory items will ship with the agent.
  5. Click Publish to Store.

A free agent goes live right away (Live in the Store), and you can share its link. A paid agent is Submitted for Review first.

Listing status

After you publish, the Publish button in the top bar becomes a listing button that shows the agent's status. The Neurons section shows the same status in a card.

  • Published: published privately, not in the store.
  • Pending review: a paid listing is waiting for review.
  • Live on Store: Users can find and install it. Choose View store listing to open its page.
  • Listing rejected: the review turned it down. The Rejection Feedback says why. Choose Fix and resubmit, change what's asked, and submit again.
  • Finish listing: the listing is missing details. Choose Complete store listing.
  • Suspended or Delisted: the agent was taken off the store. The card shows the reason and the support address to contact about your case.

Change a published agent

A published workflow is read-only on the canvas; you can still run it and edit its memory. To change it, open the listing button and choose Unpublish to edit, then Unpublish in Unpublish this agent?. The agent is removed from the Agent Store, Users who already have it can still use it from My Agents, and the workflow unlocks for editing. Unpublishing also removes the memory that shipped with the agent: Users' existing conversations lose the FROM plus your name items. Your next publish ships a new set with the new version. Publish again when you are done; see Publishing and updates.

To change only the store listing, choose Update listing. It still needs a new version number and a What changed? note, and a paid agent goes back to review.

When an action or event you use is turned off

If an administrator turns off, or sets a date to turn off, an app action or event used by one of your Workflows or published Agents, you get an email, and another if the date is cancelled. Replace the action or event before the date; see App connections. Users are not emailed, but a paused trigger shows them the message.

Write a good description

  • Start with what the agent does, in one sentence.
  • Describe the inputs it expects and the results it makes.
  • List concrete uses.
  • Mention anything it needs, such as app connections.

Limits

  • Agent name: up to 100 characters.
  • Short description: up to 200 characters.
  • About this Agent: up to 10,000 characters.
  • Tags: up to 5 tags.
  • Key Features: up to 6 features.

Common problems

Publish is greyed out

The workflow isn't one connected flow, has a loop, or has no neurons. Hover over Publish to see which, then connect or remove the neurons it names.

A memory reference blocks publishing

A neuron refers to a memory that won't ship with the agent, so Users' copies couldn't read it. Click Open Memory, then turn on Ships with the agent for that memory, or remove the reference.

Agent name is required

Each listing needs an Agent name, a short description, About this Agent and a Category. The dialog jumps to the first missing field.

Restore is greyed out in Versions

A published workflow can't be changed, so earlier versions can't be restored. Unpublish first.

Publishing your agent - Docs