Actions15
- Table Actions
- Table Record Actions
Overview
This node operation "Add Member" for the "Table" resource allows you to add a user as a member to a specific table within the Pipefy database system. It is useful in scenarios where you want to manage access control and collaboration by assigning roles to users on particular tables.
Practical examples include:
- Adding a new team member with "Member" role to collaborate on a project table.
- Assigning an "Admin" role to a user who needs elevated permissions on a table.
- Automating membership management when onboarding or offboarding users from specific tables.
Properties
| Name | Meaning |
|---|---|
| Table ID | The unique identifier of the table to which the member will be added. |
| User Email | The email address of the user to add as a member to the table. |
| Role | The role assigned to the new member on the table. Possible values: "Admin", "Member". |
Output
The output JSON contains the details of the table relation after adding the member. This typically includes information about the membership association between the user and the table, such as user details and their assigned role.
Example output structure (simplified):
{
"tableRelation": {
"userEmail": "user@example.com",
"roleNames": ["member"],
"tableId": "table_123"
}
}
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Pipefy database API.
- Requires a Pipefy-specific API authentication token.
- The node uses GraphQL mutations to interact with the Pipefy backend.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing Required Fields: Errors occur if "Table ID" or "User Email" are not provided. Ensure these fields are filled correctly.
- Invalid Email Format: If the user email is malformed, the API may reject the request.
- Insufficient Permissions: The API key used must have permission to modify table memberships; otherwise, the operation will fail.
- Role Value Errors: Only "admin" or "member" are valid roles. Using other values will cause errors.
- API Request Failures: Network issues or invalid credentials can cause failures. Verify connectivity and credential validity.
- Error Messages: The node throws errors with messages indicating missing fields or unsupported operations. Follow the message guidance to resolve.