Actions21
Overview
This node integrates with a project management API to create new projects within an external system. It is designed to facilitate the automation of project creation workflows by allowing users to specify key project details such as name, client association, budget, and pricing model. This node is beneficial in scenarios where teams want to automate project setup based on incoming data or triggers, for example, creating a new project automatically when a sales deal is closed or when a client onboarding process reaches a certain stage.
Practical examples:
- Automatically creating a new project in the system when a new client signs up.
- Setting up projects with predefined budgets and pricing models based on templates.
- Running dry runs to validate project creation parameters without affecting live data.
Properties
| Name | Meaning |
|---|---|
| Emoji | Emoji symbol representing the project (optional). |
| Name | The name/title of the project (required). |
| Is Confirmed? | Boolean flag indicating whether the project is confirmed or tentative. |
| Budget | Numeric value specifying the budget allocated for the project. |
| Client ID | Numeric identifier linking the project to a specific client (required). |
| Pricing Model | Pricing approach for the project; options include: Fixed Price, Time and Materials, Non-Billable. |
| Dry Run | Boolean flag to simulate the operation without making actual changes to the external system. |
| Options | Additional optional settings (empty collection placeholder, no specific options defined here). |
Output
The node outputs an array containing JSON objects representing the created project(s). Each JSON object includes the details of the newly created project as returned by the external API. If the "Dry Run" option is enabled, the output simulates the creation without persisting changes.
No binary data output is indicated in the source code.
Dependencies
- Requires access to the external project management API via an authenticated connection.
- Needs configuration of an API authentication token or key within n8n credentials (generic API key credential).
- Relies on internal helper modules for executing operations related to projects.
Troubleshooting
- Common issues:
- Missing required fields such as "Name" or "Client ID" will likely cause errors from the API.
- Incorrect or expired API credentials can lead to authentication failures.
- Using invalid values for "Pricing Model" may result in validation errors.
- Error messages:
"Unsupported resource"error if the resource parameter is set incorrectly.- API error messages returned in the
errorfield of the output JSON whencontinueOnFailis enabled.
- Resolutions:
- Ensure all required properties are provided and valid.
- Verify API credentials and permissions.
- Use the "Dry Run" option to test inputs before actual execution.
Links and References
- No direct links available from the source code.
- Refer to the external project management API documentation for detailed information on project creation parameters and responses.