Tallyfy icon

Tallyfy

Interact with Tallyfy workflow automation platform
Join our community

Actions54

Overview

This node integrates with the Tallyfy workflow automation platform to report a problem or blocker on a specific task by adding a comment marked as a problem. It is useful in scenarios where users need to flag issues directly within a task's comment thread, enabling better tracking and resolution of blockers during workflow execution.

For example, if a team member encounters a blocker preventing task completion, they can use this node to report the problem with a detailed comment. This helps notify relevant stakeholders and triggers any automated handling configured for problem reports in Tallyfy.

Properties

Name Meaning
Task ID The unique identifier of the task on which the problem is being reported (required).
Comment Content The content of the problem report comment; supports HTML formatting (required).

Output

The node outputs the JSON response from the Tallyfy API after reporting the problem. This typically includes details of the created problem comment such as its ID, content, timestamps, and related metadata.

The output structure is:

{
  "json": {
    // Problem comment object returned by Tallyfy API
  }
}

No binary data is produced 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 specified in credentials.
  • Requires the organization ID to construct API endpoints.
  • Proper configuration of the Tallyfy API credentials in n8n is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing Task ID will cause the API call to fail.
    • Insufficient permissions or invalid API credentials may result in authentication errors.
    • Network connectivity issues can prevent successful API requests.

  • Error Messages:

    • "404 Not Found": The specified Task ID does not exist or is inaccessible.
    • "401 Unauthorized": API credentials are invalid or missing.
    • "400 Bad Request": Required parameters like comment content are missing or malformed.

  • Resolutions:

    • Verify that the Task ID is correct and accessible within the organization.
    • Ensure the API key credential is correctly set up and has appropriate permissions.
    • Confirm that the comment content is provided and properly formatted.

Links and References

Discussion