When phone call ended in Trengo, sync it to Human in the Loop.
When a phone call ends in Trengo, pass call notes to Human in the Loop for human review.
See all Trengo + Human in the Loop integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Trengo Explore Trengo →
TriggersFires when a new support ticket or chat conversation starts in Trengo.
Fires when a ticket's status changes in Trengo.
Fires when a ticket in Trengo is assigned to an agent.
Fires when a ticket in Trengo breaches its response SLA.
Creates a new ticket in Trengo.
Updates a ticket's status in Trengo.
Assigns a ticket in Trengo to an agent.
Posts a reply or internal note on a ticket or conversation in Trengo.
Human in the Loop Explore Human in the Loop →
TriggersFires when an Human in the Loop agent finishes a task or run.
Fires when an Human in the Loop agent finishes a call or conversation.
Fires when an Human in the Loop agent marks a lead qualified.
Triggers an Human in the Loop agent or tool with a set of inputs.
Has an Human in the Loop agent place an outbound call.
Adds a lead to an outreach campaign in Human in the Loop.
Common questions
Can Knit build “When phone call ended in Trengo, sync it to Human in the Loop.” between Trengo and Human in the Loop?
Yes — describe it in the box above and Knit's Integrations Agent researches Trengo and Human in the Loop's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.