Actions20
Overview
The Plutio Project Get operation node retrieves project information from the Plutio API. It allows you to filter projects by contributor (using their email, name, or ID) and/or by project name or ID. This node is useful for automating workflows that require fetching details about specific projects or listing projects associated with a particular contributor.
Common scenarios:
- Fetching all projects a specific user is contributing to.
- Looking up a project by its name or unique identifier.
- Integrating project data into reporting, notifications, or further automation steps.
Example use cases:
- Automatically retrieve and list all projects for a given team member.
- Find a project by its name to update or process it in subsequent workflow steps.
Properties
| Name | Type | Meaning |
|---|---|---|
| Options | Collection | A group of optional filters for retrieving projects. |
| └ Contributor's Email, Name or ID | Options | Select or specify a contributor to filter projects they are involved in. |
| └ Project Name or ID | Options | Select or specify a project by name or ID to fetch a specific project. |
Output
The output is an array of project objects matching the provided filters. Each object contains the project's details as returned by the Plutio API. The structure typically includes fields such as:
{
"_id": "string",
"name": "string",
"contributors": ["string", ...],
// ...other project fields as defined by Plutio
}
- If no projects match the criteria, the output will be an empty array.
Dependencies
- External Service: Requires access to the Plutio API.
- API Credentials: You must configure valid Plutio API credentials (
plutioApi) in n8n. - n8n Configuration: No additional environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Contributor or Project ID: If the specified contributor or project does not exist, the result will be empty.
- Missing Credentials: If Plutio API credentials are not set up, the node will throw an authentication error.
- API Rate Limits: Excessive requests may trigger rate limiting on the Plutio API.
Error messages:
"Request failed with status code 401": Check your Plutio API credentials."Contributor not found"or"Project not found": Ensure the provided values are correct and exist in Plutio."Network Error": Verify network connectivity and Plutio service availability.