When new,updated or deleted client in MyTime, sync it to AMcards.com.
When client details are created, updated, or deleted in MyTime, send a physical card via AMcards.com.
See all MyTime + AMcards.com 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.
MyTime Explore MyTime →
TriggersFires when a new booking or appointment is made in MyTime.
Fires when a booking in MyTime is changed or canceled.
Fires when a new customer books for the first time in MyTime.
Creates a new booking or appointment in MyTime.
Cancels or moves a booking in MyTime.
Creates or updates a customer record in MyTime.
Adds a booking from MyTime to a connected calendar.
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.
Common questions
Can Knit build “When new,updated or deleted client in MyTime, sync it to AMcards.com.” between MyTime and AMcards.com?
Yes — describe it in the box above and Knit's Integrations Agent researches MyTime and AMcards.com'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.