When new stock notification request in Back In Stock - Restock Alerts, sync it to Flodesk.
When a back-in-stock request is created in Back In Stock, subscribe the customer to a Flodesk segment.
See all Back In Stock - Restock Alerts + Flodesk 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.
Back In Stock - Restock Alerts Explore Back In Stock - Restock Alerts →
TriggersFires when a new alert or notification is created in Back In Stock - Restock Alerts.
Fires when someone acknowledges an alert in Back In Stock - Restock Alerts.
Sends a push notification through Back In Stock - Restock Alerts.
Sends an SMS or voice notification via Back In Stock - Restock Alerts.
Schedules a reminder notification in Back In Stock - Restock Alerts.
Flodesk Explore Flodesk →
TriggersFires when a new subscriber is added in Flodesk.
Fires when a contact unsubscribes in Flodesk.
Fires when a subscriber opens or clicks a campaign in Flodesk.
Creates or updates a subscriber in Flodesk.
Unsubscribes a contact in Flodesk.
Adds a subscriber to a list or segment in Flodesk.
Sends a one-off transactional email via Flodesk.
Common questions
Can Knit build “When new stock notification request in Back In Stock - Restock Alerts, sync it to Flodesk.” between Back In Stock - Restock Alerts and Flodesk?
Yes — describe it in the box above and Knit's Integrations Agent researches Back In Stock - Restock Alerts and Flodesk'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.