Create CRM contacts from app records
When a new record is created in Glide, create or update the contact in Mapsly.
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.
Mapsly Explore Mapsly →
TriggersFires when a new contact or lead is added to Mapsly.
Fires when a field on a contact changes in Mapsly.
Fires when a deal, case or record moves to a new stage in Mapsly.
Fires when a deal is marked won in Mapsly.
Creates or updates a contact in Mapsly.
Creates a new deal in Mapsly.
Moves a deal or record to a new stage in Mapsly.
Logs a call, email, or note against a record in Mapsly.
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.
More Mapsly + Glide workflows
See all Mapsly + Glide integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create CRM contacts from app records” between Mapsly and Glide?
Yes — describe it in the box above and Knit's Integrations Agent researches Mapsly and Glide'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 a CRM contact?
Yes. When a record is created in Glide, Mapsly can create or update the matching contact, company or deal.
Will CRM changes show up in my app?
When a deal or contact changes in Mapsly, the matching record in Glide can be updated so app users always see current data.