Unified commerce platform
VTEX currently provides 17 actions a workflow can run. Use those building blocks to connect customer and order activity to the relationship record behind it.
Get Product By ID
Find a product in your catalog by it's id
Create New Product
Create a new product in your catalog
Update a Product
Update a product in your catalog
Get Brand List
Find all Brands in your catalog
Get Brand By ID
Find a Brand in your catalog by it's id
Create new Brand
Create a new Brand to your catalog
Update Brand
Update a Brand in your catalog
Delete Brand
Delete a Brand in your catalog by it's id
Get Category
Find a Category in your catalog by it's id
Get SKU By Product ID
Find a Sku in your catalog by a Product id
Create New Sku
Create a new SKU to your catalog
Create New Sku File
Create a new SKU File to your catalog
Get Client List
Find all Clients
Get Client By ID
Find a Client by Id
Get Order By ID
Find a Order by Id
Get Orders List
Find Orders
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 VTEX 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
Get Product By ID
Combine VTEX with another integration and Coherence records to connect customer and order activity to the relationship record behind it.
Starts with
A Coherence workflow starts
Finishes with
Get Product By ID, then preserve the outcome in Coherence
The exact authentication fields depend on VTEX. The workflow structure stays straightforward:
Authorize the VTEX 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 VTEX or provide a complementary trigger or action.
VTEX currently provides 17 actions a workflow can run. Use those building blocks to connect customer and order activity to the relationship record behind it.
VTEX currently lists 0 triggers and 17 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 VTEX 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.
