Document abandoned carts for personalized outreach

When a shopper leaves items behind in Custom Gateway OMS, append the cart details to a note in Journey so sales teams can follow up directly.

Try:

See all Custom Gateway OMS + Journey integrations or talk to a human

Trusted by teams already building on Knit·

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.

Custom Gateway OMS Explore Custom Gateway OMS →

Triggers

New order

Fires when a customer places a new order in Custom Gateway OMS.

Order status changed

Fires when an order in Custom Gateway OMS is paid, fulfilled, refunded or disputed.

New customer

Fires when a new customer account is created in Custom Gateway OMS.

Cart abandoned

Fires when a customer abandons their cart before completing checkout in Custom Gateway OMS.

Actions

Create or update product

Creates or updates a product or listing in Custom Gateway OMS.

Update order

Updates an order's status or fulfillment details in Custom Gateway OMS.

Make a custom API request

Sends a custom API request to Custom Gateway OMS for actions not covered by a dedicated action.

Journey Explore Journey →

Triggers

New note created

Fires when a new note or document is created in Journey.

Note updated

Fires when an existing note or document changes in Journey.

Document viewed or shared

Fires when a document in Journey is viewed or shared with someone.

Actions

Create a document from a template

Generates a new document in Journey from a saved template.

Create or append to a note

Creates a note in Journey or adds text to an existing one.

Convert a document to PDF

Converts a file in Journey to PDF.

Publish or share a document

Publishes a document from Journey or shares it by link.

Send affiliate agreements automatically upon approval When a new affiliate is approved in Custom Gateway OMS, instantly dispatch a tax or partnership document for signature through Journey. See details

Update store records when legal documents are dispatched As soon as a contract is sent out via Journey, make a custom API request to Custom Gateway OMS to update the partner's onboarding status. See details

See all Custom Gateway OMS + Journey integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Document abandoned carts for personalized outreach” between Custom Gateway OMS and Journey?

Yes — describe it in the box above and Knit's Integrations Agent researches Custom Gateway OMS and Journey'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.

Why pair Journey with an e-commerce platform like Custom Gateway OMS?

This pairing allows store owners to automatically send agreements for signature or record customer notes whenever key shop events like affiliate approvals happen.

Is it possible to notify Custom Gateway OMS when a document is sent in Journey?

Yes, when a document is dispatched for signature in Journey, a custom API call can be made to update partner status in Custom Gateway OMS.