When marketplace - trial did not convert in TrainHeroic, sync it to LeadDyno.
When a marketplace trial does not convert in TrainHeroic, update affiliate referral status in LeadDyno.
See all LeadDyno + TrainHeroic integrations or talk to a human
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.
LeadDyno Explore LeadDyno →
TriggersFires when a new lead or contact is captured in LeadDyno.
Fires when a contact enters an automation in LeadDyno.
Fires when a field on a contact changes in LeadDyno.
Fires when a contact unsubscribes in LeadDyno.
Creates or updates a contact in LeadDyno.
Adds a contact to a workflow or campaign in LeadDyno.
Sends an email or message to a contact via LeadDyno.
Changes a contact's tags in LeadDyno.
TrainHeroic Explore TrainHeroic →
TriggersFires when a new member, client or user joins in TrainHeroic.
Fires when someone books a class or session in TrainHeroic.
Fires when a workout, habit, journal entry or goal is logged in TrainHeroic.
Creates or updates a member's profile in TrainHeroic.
Books a class or session for a client in TrainHeroic.
Logs a workout, habit or data point in TrainHeroic.
Common questions
Can Knit build “When marketplace - trial did not convert in TrainHeroic, sync it to LeadDyno.” between LeadDyno and TrainHeroic?
Yes — describe it in the box above and Knit's Integrations Agent researches LeadDyno and TrainHeroic'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.