gotoHuman Trigger icon

gotoHuman Trigger

Triggers when a gotoHuman event occurs

gotoHuman Trigger

AI-generated

Overview

This node acts as a trigger for events related to the gotoHuman platform. It listens for specific events such as the completion of a review, messages or tool results for an agent, or the submission of an agent trigger form. When one of these events occurs, the node activates and outputs the event data. This is useful for automating workflows that depend on these specific triggers, such as processing completed reviews, handling agent communications, or responding to form submissions.

Use Case Examples

  1. Trigger a workflow when a review is completed using a specified review template.
  2. Start a workflow when an agent receives a message or tool result.
  3. Activate a workflow upon submission of a specific agent trigger form.

Properties

Name Meaning
Trigger On Specifies the event type that triggers the node. Options include Completed Review, Message or Tool Result for Agent, and Submitted Agent Trigger Form.
Review Template Select or specify the ID of a review template to listen for when the trigger is set to Completed Review. This property is required only for the Completed Review trigger.
Trigger Form Select or specify the ID of a trigger form to listen for when the trigger is set to Submitted Agent Trigger Form. This property is required only for the Submitted Agent Trigger Form trigger.
Agent Select or specify the ID of an agent to listen for when the trigger is set to Message or Tool Result for Agent. This property is required only for the Message or Tool Result for Agent trigger.

Output

JSON

  • body - The JSON payload received from the gotoHuman webhook event, containing details about the triggered event.

Dependencies

  • An API key credential for the gotoHuman API is required to authenticate and receive webhook events.

Troubleshooting

  • Ensure the webhook URL is correctly configured in the gotoHuman platform to send events to this node.
  • Verify that the correct trigger type and associated resource IDs (review template, trigger form, or agent) are selected to match the expected events.
  • Check API credentials to ensure the node can authenticate with the gotoHuman service.
  • Common errors may include missing or invalid webhook data, which can be resolved by confirming the webhook setup and event configuration on the gotoHuman side.

Discussion