Create Member

Go to Product

Adds an existing user to a project with a given role. The user must already have a NodePit Runner account; this does not send an invite email to sign up.

Options

Body

The JSON request body. Pre-filled with an example which is derived from the schema.

Validate JSON
Checks “Body” against the JSON schema of the API. This happens on demand only, i.e. a failed check does not prevent the node from being executed — ultimately, the API itself decides what it accepts.
Body: Validation
Result of the last “Validate JSON” run, i.e. a confirmation or the list of schema violations. Not saved with the node settings.
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: Stringified ObjectId (hexadecimal string with 24 characters). See ObjectId
  • Kind: Identifies this object as a project member.
  • User: A NodePit Runner user account.
  • Project: Stringified ObjectId (hexadecimal string with 24 characters). See ObjectId
  • Role: A project member's permission level, each including everything below it: owner (full control, including managing members and deleting the project), maintainer (can also create and edit environments and schedules), operator (can also trigger and manage runs), or reader (view-only).
  • Deletable: Whether this membership can be removed — always false for a project's sole remaining owner, since every project must keep at least one.
  • Created At: When this membership was created.
  • Updated At: When this membership was last changed (e.g. its role).
  • Created By: A NodePit Runner user account.
  • Updated By: A NodePit Runner user account.

Raw Response: Returns the raw response in a single row with the following columns:

  • body: Response body
  • status: HTTP status code

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
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

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

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.