Tallyfy icon

Tallyfy

Interact with Tallyfy workflow automation platform

Overview

This node interacts with the Tallyfy workflow automation platform, specifically managing process instances. The "Archive" operation for the "Process" resource allows users to archive (soft delete) a specific process instance by its ID. Archiving a process is useful when you want to mark a process as inactive or remove it from active views without permanently deleting it.

Practical scenarios include:

  • Cleaning up completed or obsolete processes while retaining their data for audit purposes.
  • Managing process lifecycle by archiving processes that are no longer relevant.
  • Automating process management workflows where processes are archived based on certain triggers or conditions.

Properties

Name Meaning
Process ID The unique identifier of the process to archive. This is required to specify which process instance should be archived.

Output

The output JSON contains the response from the Tallyfy API after attempting to archive the specified process. Typically, this will be an object representing the archived process or confirmation of the archive action. If multiple input items are processed, the output will be an array of such objects corresponding to each input.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Tallyfy API.
  • The node uses the base URL https://go.tallyfy.com/api or a custom base URL if provided in credentials.
  • Requires the organization ID configured in the credentials to construct API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Process ID: The node requires a valid process ID; ensure the ID is correct and exists.
    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
    • Network or API endpoint errors: Check network connectivity and that the Tallyfy API service is reachable.
  • Error messages:

    • Errors returned from the API will be included in the output if "Continue On Fail" is enabled.
    • Common HTTP errors like 401 Unauthorized indicate authentication problems.
    • 404 Not Found may indicate the process ID does not exist or is already archived/deleted.

Resolving these typically involves verifying input parameters, credentials, and API access rights.

Links and References

Discussion