PlaneInstall

Overview

This node integrates with the Plane API to manage project modules. Specifically, the Module - Create operation allows users to create a new module within a specified project by providing essential details such as the module's name and optional additional information.

Common scenarios where this node is beneficial include:

• Organizing a project into smaller functional or thematic units (modules) for better management.
• Automating the creation of modules during project setup or workflow automation.
• Integrating module creation into larger workflows that involve project planning and issue tracking.

Practical example:

• A project manager wants to automatically create a new development module named "Frontend" in a project whenever a new feature request is received, including setting its start date, target completion date, status, and assigning team members.

Properties

Name	Meaning
Project ID	The unique identifier of the project where the module will be created.
Name	The name of the module to be created.
Additional Fields	Optional extra details about the module. These include:
	- Description: Text describing the module.
	- Start Date: The starting date/time of the module.
	- Target Date: The estimated completion date/time of the module.
	- Status: Current status of the module. Options are: Backlog, Cancelled, Completed, In Progress, Paused, Planned (default).
	- Lead: User ID of the person leading the module.
	- Members: Comma-separated list of user IDs who are members of this module.

Output

The output JSON contains the response from the Plane API after creating the module. This typically includes all properties of the newly created module such as its ID, name, description, dates, status, lead, members, and any other metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

• Requires an active Plane API connection configured in n8n with appropriate credentials (an API key or token).
• The node uses internal helper functions to make HTTP requests to the Plane API endpoints.
• The projectId must correspond to an existing project accessible via the Plane API.

Troubleshooting

• Missing or invalid Project ID: Ensure the Project ID provided exists and is correct; otherwise, the API call will fail.
• Invalid date formats: Dates in Start Date and Target Date fields should be valid ISO 8601 datetime strings.
• Incorrect member IDs: The Members field expects valid user IDs separated by commas; invalid IDs may cause errors.
• API authentication errors: Verify that the Plane API credentials are correctly set up in n8n.
• Network or API errors: Check network connectivity and Plane API service status if requests fail unexpectedly.

Common error messages:

• "No binary data exists on item!" — Not applicable here since no binary data is used.
• API error responses indicating invalid parameters or unauthorized access should be resolved by verifying input values and credentials.

Links and References

• Plane API Documentation (for detailed API endpoint info)
• n8n documentation on Creating Custom Nodes
• General REST API usage guidelines in n8n: HTTP Request Node