Actions36
- Activity Actions
- Contact Actions
- Customer Actions
- Data Proxy Actions
- Document Actions
- Employer Actions
- Lead Actions
- Meeting Actions
- Meeting Summary Actions
- Report Actions
- Workflow Actions
Workflow → Get a Workflow
AI-generatedOverview
This node, named "Surense," is designed to interact with the Surense API, providing access to various resources including workflows. Specifically, for the "Workflow" resource and the "Get a Workflow" operation, it retrieves detailed information about a single workflow identified by its unique ID (UUID format). This functionality is useful in automation scenarios where you need to fetch and process workflow details dynamically, such as monitoring workflow status, auditing workflow configurations, or integrating workflow data into other systems.
Practical examples include:
- Fetching a specific workflow's configuration to display or log it.
- Using workflow details to trigger conditional logic in an automation.
- Integrating workflow metadata into reporting dashboards.
Properties
| Name | Meaning |
|---|---|
| מזהה תהליך | The unique identifier (UUID) of the workflow to retrieve. Example: 123e4567-e89b-12d3-a456-426614174000 |
Output
The node outputs an array where each element corresponds to the result of processing one input item. For the "Get a Workflow" operation, the output JSON contains the detailed data of the requested workflow fetched from the Surense API. The exact structure depends on the API response but typically includes workflow metadata such as ID, name, status, type, steps, and other relevant properties.
If an error occurs during execution and the node is configured to continue on failure, the output will contain an object with an error field describing the issue.
The node does not output binary data.
Dependencies
- Requires an active connection to the Surense API.
- Needs an OAuth2 API credential configured in n8n to authenticate requests.
- Pagination fields are available but may not be relevant for single workflow retrieval.
Troubleshooting
Common issues:
- Invalid or missing workflow ID: Ensure the provided UUID is correct and exists in Surense.
- Authentication errors: Verify that the OAuth2 credentials are correctly set up and have necessary permissions.
- Network or API downtime: Check connectivity and Surense service status.
Error messages:
"error": "Workflow not found": The specified workflow ID does not exist; verify the ID.- Authentication failures usually indicate invalid or expired tokens; reauthenticate the credential.
- Other API errors will be passed through in the
errorfield if "Continue On Fail" is enabled.
Links and References
- Surense API Documentation (hypothetical link as no real URL provided)
- n8n OAuth2 Credential Setup
- UUID Format Reference