When a contact's status changes in Lofty, automatically schedule a greeting card campaign via AMcards.com.
When a contact's status changes in Lofty, automatically schedule a greeting card campaign via AMcards.com.
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.
AMcards.com Explore AMcards.com →
TriggersFires when a new print or mail job is submitted to AMcards.com.
Fires when a print or mail job in AMcards.com finishes or ships.
Sends a document or design to AMcards.com to print.
Sends a physical postcard or letter via AMcards.com.
Looks up the status of a print or mail job in AMcards.com.
Lofty Explore Lofty →
TriggersFires when a new contact or lead is added to Lofty.
Fires when a field on a contact changes in Lofty.
Fires when a deal, case or record moves to a new stage in Lofty.
Fires when a deal is marked won in Lofty.
Creates or updates a contact in Lofty.
Creates a new deal in Lofty.
Moves a deal or record to a new stage in Lofty.
Logs a call, email, or note against a record in Lofty.
Common questions
Can Knit build “When a contact's status changes in Lofty, automatically schedule a greeting card campaign via AMcards.com.” between AMcards.com and Lofty?
Yes — describe it in the box above and Knit's Integrations Agent researches AMcards.com and Lofty'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.