Open issues from app requests
When a new request record is created in Glide, create an issue in Ambee.
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.
Ambee Explore Ambee →
TriggersFires when a job, build or file conversion finishes in Ambee.
Fires when a job, build or API request fails in Ambee.
Calls an Ambee endpoint with data from an earlier step.
Creates a PDF, image or converted file with Ambee.
Checks or enriches a phone number, address or IP with Ambee.
More Glide + Ambee workflows
See all Glide + Ambee integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Open issues from app requests” between Glide and Ambee?
Yes — describe it in the box above and Knit's Integrations Agent researches Glide and Ambee'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 a record in Glide create an issue in Ambee?
Yes. When a record such as a bug report or request is created in Glide, Ambee can open an issue or run a workflow.
Can developer events update my app?
When an issue closes or a deploy finishes in Ambee, the related record in Glide can be updated automatically.