When sent fax completed in HumbleFax, sync it to Kustomer.
When a sent fax completes in HumbleFax, update customer conversation timelines in Kustomer.
See all HumbleFax + Kustomer 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.
HumbleFax Explore HumbleFax →
TriggersFires when a new fax is received in HumbleFax.
Fires when an outbound fax sent via HumbleFax fails to deliver.
Sends a document as a fax via HumbleFax.
Looks up the delivery status of a fax in HumbleFax.
Kustomer Explore Kustomer →
TriggersFires when a new support ticket or chat conversation starts in Kustomer.
Fires when a ticket's status changes in Kustomer.
Fires when a ticket in Kustomer is assigned to an agent.
Fires when a ticket in Kustomer breaches its response SLA.
Creates a new ticket in Kustomer.
Updates a ticket's status in Kustomer.
Assigns a ticket in Kustomer to an agent.
Posts a reply or internal note on a ticket or conversation in Kustomer.
Common questions
Can Knit build “When sent fax completed in HumbleFax, sync it to Kustomer.” between HumbleFax and Kustomer?
Yes — describe it in the box above and Knit's Integrations Agent researches HumbleFax and Kustomer'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.