Actions26
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
- Project Indicators Actions
Overview
This node interacts with a project management API to perform various workflow actions related to project documents, among other resources. Specifically, the "Get Project Document Url" operation retrieves the URL of a specified project document by its ID. This is useful when you want to programmatically access or share direct links to documents stored within a project management system.
Practical examples include:
- Automatically fetching and sending document URLs in notifications or reports.
- Integrating document links into other systems or dashboards.
- Accessing documents for further processing or review without manual lookup.
Properties
| Name | Meaning |
|---|---|
| Document ID * | The unique identifier of the project document whose URL you want to retrieve. |
Output
The output contains a JSON object with the details returned from the API call to get the project document URL. Typically, this will include at least the URL string pointing to the document location. The exact structure depends on the API response but generally provides direct access information to the requested document.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Pulse API service.
- The node depends on the Pulse API helper utilities bundled within the node's codebase.
- Proper configuration of the API credentials in n8n is necessary to successfully execute requests.
Troubleshooting
Common issues:
- Invalid or missing Document ID: Ensure the Document ID is correctly provided and exists in the system.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Unsupported resource or operation errors: Confirm that the selected resource is "Project Document" and the operation is "Get Project Document Url".
Error messages:
"The operation "getProjectDocumentUrl" is not supported for resource "projectDocuments"!"— This indicates a mismatch in resource-operation selection; verify inputs.- API errors related to authorization or network issues will be passed through; check API credentials and connectivity.
To handle failures gracefully, enable the "Continue On Fail" option to allow the workflow to proceed even if some executions fail.
Links and References
- Pulse API Documentation (Replace with actual API docs link)
- n8n documentation on Creating Custom Nodes