Tallyfy icon

Tallyfy

Interact with Tallyfy workflow automation platform

Overview

This node interacts with the Tallyfy workflow automation platform, specifically focusing on managing process instances (runs). The "Get" operation for the "Process" resource retrieves detailed information about a specific process instance by its ID. This is useful when you want to fetch the current state, metadata, or details of a particular workflow run within your organization.

Common scenarios include:

  • Monitoring the status or progress of a specific process instance.
  • Retrieving process details to trigger conditional logic in an automation.
  • Auditing or reporting on individual workflow runs.

For example, you might use this node to get the details of a process instance after launching it, to check if it has completed or to extract data from it for further processing.

Properties

Name Meaning
Process ID The unique identifier of the process instance to retrieve.

Output

The output is a JSON object representing the detailed data of the requested process instance. This includes all relevant fields returned by the Tallyfy API for a process run, such as its name, status, creation date, associated blueprint, and other metadata.

The node does not output binary data for this operation.

Example output structure (simplified):

{
  "id": "string",
  "name": "string",
  "status": "string",
  "created_at": "string",
  "updated_at": "string",
  "blueprint_id": "string",
  // ... other process-specific fields
}

Dependencies

  • Requires an API key credential for authenticating with the Tallyfy API.
  • Needs the organization ID configured within the credentials.
  • The base URL defaults to https://go.tallyfy.com/api but can be overridden in credentials.

Troubleshooting

  • Invalid Process ID: If the provided Process ID does not exist or is incorrect, the API will return an error. Verify that the Process ID is correct and belongs to your organization.
  • Authentication Errors: Ensure that the API key credential is valid and has access to the specified organization.
  • Network Issues: Connectivity problems may cause request failures. Check network settings and API availability.
  • Permission Denied: The authenticated user must have permission to view the process instance.

If errors occur, enabling "Continue On Fail" allows the workflow to proceed while capturing error messages in the output.

Links and References

Discussion