When new package in LegitFit, sync it to Invoiced.
When a new package is purchased in LegitFit, generate an invoice in Invoiced.
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.
LegitFit Explore LegitFit →
TriggersFires when a new member, client or user joins in LegitFit.
Fires when someone books a class or session in LegitFit.
Fires when a workout, habit, journal entry or goal is logged in LegitFit.
Creates or updates a member's profile in LegitFit.
Books a class or session for a client in LegitFit.
Logs a workout, habit or data point in LegitFit.
Invoiced Explore Invoiced →
TriggersFires when a new invoice is created in Invoiced.
Fires when a payment is recorded in Invoiced.
Fires when an invoice in Invoiced passes its due date unpaid.
Fires when a new expense is recorded in Invoiced.
Creates a new invoice in Invoiced.
Records a payment against an invoice in Invoiced.
Creates a new expense entry in Invoiced.
Syncs a customer's billing record in Invoiced.
Common questions
Can Knit build “When new package in LegitFit, sync it to Invoiced.” between LegitFit and Invoiced?
Yes — describe it in the box above and Knit's Integrations Agent researches LegitFit and Invoiced'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.