Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy GraphQL API to perform various operations on Pipefy resources. Specifically, for the User resource and the Get Current operation, it retrieves information about the currently authenticated user. This is useful in scenarios where you need to fetch details about the user who is making the API request, such as their ID, name, email, or other profile information.
Practical examples include:
- Automatically personalizing workflows based on the current user's identity.
- Logging or auditing actions performed by the user.
- Fetching user-specific settings or permissions before proceeding with further automation steps.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Pipefy API. Options: - Service Account - Personal Access Token |
Output
The node outputs a JSON array containing the data of the current user retrieved from Pipefy. The structure typically includes fields such as user ID, name, email, and other profile-related information as provided by the Pipefy API.
If the node supports binary data output (not indicated here), it would be summarized accordingly, but this operation primarily returns JSON user data.
Dependencies
- Requires an active connection to the Pipefy GraphQL API.
- Needs either a service account credential or a personal access token credential configured in n8n for authentication.
- No additional external dependencies beyond the Pipefy API and proper credentials.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials. Invalid or expired tokens will cause failures.
- API connectivity issues: Network problems or Pipefy API downtime can prevent successful requests.
- Permission errors: The authenticated user must have sufficient permissions to access user data; otherwise, the API may return authorization errors.
- Unexpected response structure: If Pipefy changes its API schema, the node might not parse the user data correctly.
To resolve these issues:
- Verify and refresh credentials if needed.
- Check network connectivity.
- Confirm user permissions in Pipefy.
- Review any error messages returned by the node for specific guidance.