Skip to main content
POST
Share a workflow
The following request shares a workflow with the whole organization for viewing, gives one user edit access, and lets one team run it:
A team_id is a team’s group ID, which is not yet available from a public API. To share a workflow with a team, use the share panel in the Studio.
Credentials typed directly into a node are visible to anyone with read access, including in published versions. This covers HTTP Request auth, header, and query values, A2A keys, a Guardrails key, a Crypto secret, and the trigger’s webhook secret. Use a credential from the picker in any workflow you share.

Authorizations

x-api-key
string
header
required

Lyzr API key. Studio session keys (agk_, ags_) and durable sk- keys are accepted. Required on every endpoint except GET /node-types and a webhook-triggered execute that carries X-Webhook-Secret.

Path Parameters

id
string
required

Workflow ID

Body

application/json

Share payload

access_level
enum<string>

The group tier.

Available options:
private,
organisation,
public
Example:

"organisation"

org_access_level
enum<string>

What an organization-wide share grants: read (view) or write (edit). Only used when access_level is organisation.

Available options:
read,
write
Example:

"read"

shared_with
object[]

Individual users and the access each one gets.

shared_with_teams
object[]

Teams and the access each one gets.

Response

OK

_id
string
group_id
string
root_resource_id
string
root_resource_type
string
access_level
enum<string>
Available options:
private,
organisation,
public,
read,
write,
execute
org_access_level
enum<string>
Available options:
read,
write
shared_with
object[]
shared_with_teams
object[]
agent_ids
string[]
superflow_ids
string[]
user_id
string
user_email
string
org_id
string