Create orders from app records
When a record is marked approved in Glide, create an order in Horoshop.
Google for Startups AcceleratorHow 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.
Glide Explore Glide →
TriggersFires when a new record is added to an app built in Glide.
Fires when a record changes in an Glide app.
Fires when a record is deleted in an Glide app.
Adds a new record to an app built in Glide.
Updates an existing record in an Glide app.
Removes a record from an Glide app.
Horoshop Explore Horoshop →
TriggersFires when a customer places a new order in Horoshop.
Fires when an order in Horoshop is paid, fulfilled, refunded or disputed.
Fires when a new customer account is created in Horoshop.
Fires when a customer abandons their cart before completing checkout in Horoshop.
Creates or updates a product or listing in Horoshop.
Updates an order's status or fulfillment details in Horoshop.
Sends a custom API request to Horoshop for actions not covered by a dedicated action.
More Glide + Horoshop workflows
See all Glide + Horoshop integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create orders from app records” between Glide and Horoshop?
Yes — describe it in the box above and Knit's Integrations Agent researches Glide and Horoshop'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.
Can store orders show up in my internal app?
Yes. When a new order is placed in Horoshop, Glide can create a record with the items, customer and status.
Can the app update the store?
Records created or updated in Glide can create orders or update product details in Horoshop.