Create or update Naamly leads when new leads appear in 97Display.
When a new lead is registered in 97Display, create or update the corresponding member profile in Naamly.
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.
Naamly Explore Naamly →
TriggersFires when a new member, client or user joins in Naamly.
Fires when someone books a class or session in Naamly.
Fires when a workout, habit, journal entry or goal is logged in Naamly.
Creates or updates a member's profile in Naamly.
Books a class or session for a client in Naamly.
Logs a workout, habit or data point in Naamly.
97Display Explore 97Display →
TriggersFires when a new page or post is published on 97Display.
Fires when a form on 97Display is submitted.
Fires when a CMS item is updated on 97Display.
Publishes or updates a page on 97Display.
Creates a new CMS item on 97Display.
Updates existing content on 97Display.
Common questions
Can Knit build “Create or update Naamly leads when new leads appear in 97Display.” between Naamly and 97Display?
Yes — describe it in the box above and Knit's Integrations Agent researches Naamly and 97Display'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.