How do I share a workflow as an app, an API endpoint or a social post?
Share a workflow as an app with its own address and form, as an API endpoint other developers call from code, or as a social post on Instagram.
You can share a workflow three ways: publish it as an app with its own address where people fill in a simple form, let other developers call the published app from their code as an API endpoint, or post what the workflow makes to a connected social account such as Instagram.
The app and the API endpoint come from one publish step: the Publish button in the workflow editor, or POST /api/v1/workflows/{id}/publish with a key that has the workflows:write scope. People who use the app see the form and the results, never the workflow canvas.
When you save the workflow, the published app reflects the changes. You can also make an app private, so only you can call it, and you can unpublish it.
Which way of sharing fits my workflow?
Pick by who will use what the workflow makes:
| You want to | Read |
|---|---|
Give people a form at your own address, such as my-tool.wireflow.ai |
Publishing Apps |
Let other developers start your workflow from their code with POST /api/v1/apps/{slug}/execute |
Let others run your workflow through the API |
| Post Reels, images and carousels to an Instagram Business or Creator account from a workflow | Publishing to Instagram |
| Plan posts on a content calendar from code or an AI agent | Plan posts on a content calendar |
What else is in the publishing section?
Two reference pages cover the same jobs from code:
- Apps API: find a published app's input keys, call it, poll the run, and read its errors and limits.
- Social Accounts: list the social accounts connected to your login, so a script or an agent can point a Social Publish node at one.
To build the workflow before you share it, start at How do I build and run AI workflows on the Wireflow canvas?.