Actions32
- Card Actions
- Organization Actions
- Pipe Actions
- Phase Actions
- Table Actions
- Table Record Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy API to manage users within an organization. Specifically, the User - Invite operation allows you to invite a new user to join a specified organization on Pipefy by providing their email and assigning them a role.
Common scenarios where this node is beneficial include:
- Automating onboarding workflows by inviting new team members to your Pipefy organization.
- Integrating user management into broader automation pipelines, such as syncing users from other systems or CRM platforms.
- Managing access control by programmatically assigning roles during invitation.
For example, you can use this node to invite a new project collaborator by specifying their email and setting their role as "Member" in your organization's Pipefy workspace.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The unique identifier of the organization to which the user will be invited. |
| The email address of the user to invite. | |
| Role | The role to assign to the invited user within the organization. Options: Admin, Member, Guest |
Output
The output JSON contains the result of the invitation mutation from the Pipefy API. It includes a success field indicating whether the invitation was successfully sent.
Example output structure:
{
"success": true
}
This confirms that the user invitation request was processed successfully.
Dependencies
- Requires an active Pipefy API key credential configured in n8n for authentication.
- Uses the Pipefy GraphQL API endpoint at
https://api.pipefy.com/graphql. - The node sends GraphQL mutation requests to invite users.
Troubleshooting
Common issues:
- Invalid or missing organization ID: Ensure the organization ID is correct and the authenticated user has permission to invite members.
- Invalid email format: Provide a valid email address.
- Insufficient permissions: The API key used must have rights to manage organization members.
- Network or API errors: Check connectivity and Pipefy service status.
Error messages:
- Errors returned from the API will typically indicate the cause, such as "Organization not found" or "Email already invited".
- If the node throws an error, verify credentials and input parameters.
- Use the "Continue On Fail" option in n8n to handle errors gracefully in workflows.