Add an Organization Member to a Team

Go to Product

This request can return various success codes depending on the context of the team:

  • 201: The member has been successfully added.
  • 202: The member needs permission to join the team and an access request has been generated.
  • 204: The member is already on the team.

If the team is provisioned through an identity provider, the member cannot join the team through Sentry.

Note the permission scopes vary depending on the organization setting "Open Membership" and the type of authorization token. The following table outlines the accepted scopes.

Open Membership
On Off
Org Auth Token
  • • org:read
  • • org:write
  • • team:write
User Auth Token
  • • org:read
  • • org:read*
  • • org:write
  • • org:read +
  •    team:write**

*Organization members are restricted to this scope. When sending a request, it will always return a 202 and request an invite to the team.

**Team Admins must have both org:read and team:write scopes in their user authorization token to add members to their teams.


Organization Slug
The slug of the organization the resource belongs to.
Member Id
The ID of the organization member to add to the team
Team Slug
The slug of the team the resource belongs to.
Result Format
Specify how the response should be mapped to the table output. The following formats are available:
  • Structured Table: Returns a parsed table with data split into rows and columns.
    • Id:
    • Slug:
    • Name:
    • Date Created:
    • Is Member:
    • Team Role:
    • Flags:
    • Access:
    • Has Access:
    • Is Pending:
    • Member Count:
    • Avatar:
  • Raw Response: Returns the raw response in a single row with the following columns:
    • body: Response body
    • status: HTTP status code

Input Ports

Configuration data.

Output Ports

Result of the request depending on the selected Result Format.
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found


This node has no views


  • No workflows found



You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.