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