Planka icon

Planka

Interact with Planka API

Actions46

Overview

The "📎 Create Attachment in Card" operation for the 📝 CARD resource allows you to attach a file (from a URL or local path) to an existing card in Planka, a project management tool. This is useful for workflows where you need to programmatically add supporting documents, images, or other files to cards as part of your automation.

Common scenarios:

  • Automatically attaching invoices, receipts, or reports generated by previous workflow steps to a task card.
  • Adding screenshots, design files, or documentation to development or design cards.
  • Linking external resources (via URL) directly to a card for easy access by team members.

Example:
After generating a PDF report in n8n, use this node to upload and attach the report to a specific Planka card for review.

Properties

Name Type Meaning
Card ID String The unique identifier of the card to which the attachment will be added.
File String The file to attach; can be a URL or a file path accessible to n8n.
Attachment Name String The display name for the attachment as it will appear in Planka.

Output

The output will be a JSON object representing the newly created attachment in Planka. While the exact structure depends on the Planka API, typical fields may include:

{
  "id": "string",            // Unique identifier of the attachment
  "name": "string",          // Name of the attachment
  "fileUrl": "string",       // URL to access/download the attached file
  "createdAt": "string",     // Timestamp of when the attachment was added
  "cardId": "string",        // ID of the card the attachment belongs to
  // ...other metadata provided by Planka
}

If the file is uploaded as binary data, the node handles it as a multipart/form-data request, but the output remains a JSON description of the attachment.

Dependencies

  • Planka API: Requires a valid Planka instance with API access enabled.
  • API Credentials: You must configure the plankaApi credential in n8n with appropriate permissions.
  • File Access: If using a file path, the n8n instance must have access to the specified file location.

Troubleshooting

Common issues:

  • Invalid Card ID: If the Card ID does not exist, the API will return an error. Double-check the ID.
  • File Not Found: If providing a file path, ensure the file exists and is accessible by the n8n server.
  • Authentication Errors: Ensure your Planka API credentials are correct and have permission to add attachments.
  • Unsupported File Types: Some file types may not be accepted by Planka; check Planka's documentation if uploads fail.

Error messages:

  • "Card not found": The specified Card ID does not exist.
  • "File missing or inaccessible": The file path or URL could not be accessed.
  • "Unauthorized": Invalid or missing API credentials.

Resolution:

  • Verify all input values.
  • Check n8n credential configuration.
  • Ensure file paths/URLs are correct and accessible.

Links and References

Discussion