Create and manage Kustomer customers, conversations, and custom objects.
Kustomer currently provides 6 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Create Customer
Creates a new customer record in Kustomer.
Create Conversation
Creates a new conversation in Kustomer.
Update Conversation
Updates an existing conversation in Kustomer.
Get Customer
Gets a customer by ID from Kustomer.
Get Custom Objects
Retrieves all custom objects (KObjects) for a given class in Kustomer.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Use a change in Coherence to run a supported Kustomer action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Customer
Combine Kustomer with another integration and Coherence records to connect support activity to the full account history and the next internal action.
Starts with
A Coherence workflow starts
Finishes with
Create Customer, then preserve the outcome in Coherence
The exact authentication fields depend on Kustomer. The workflow structure stays straightforward:
Authorize the Kustomer account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Kustomer or provide a complementary trigger or action.
Kustomer currently provides 6 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Kustomer currently lists 0 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Kustomer triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
