When new client in Arbox, sync it to Smoove.
When a new client registers in Arbox, sync contact details into Smoove marketing automation. Trigger follow-up sequences.
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.
Smoove Explore Smoove →
TriggersFires when a new lead or contact is captured in Smoove.
Fires when a contact enters an automation in Smoove.
Fires when a field on a contact changes in Smoove.
Fires when a contact unsubscribes in Smoove.
Creates or updates a contact in Smoove.
Adds a contact to a workflow or campaign in Smoove.
Sends an email or message to a contact via Smoove.
Changes a contact's tags in Smoove.
Arbox Explore Arbox →
TriggersFires when a new member, client or user joins in Arbox.
Fires when someone books a class or session in Arbox.
Fires when a workout, habit, journal entry or goal is logged in Arbox.
Creates or updates a member's profile in Arbox.
Books a class or session for a client in Arbox.
Logs a workout, habit or data point in Arbox.
Common questions
Can Knit build “When new client in Arbox, sync it to Smoove.” between Smoove and Arbox?
Yes — describe it in the box above and Knit's Integrations Agent researches Smoove and Arbox'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.