When something happens in Dinamize, sync it to Webpushr.
When subscriber details are updated in Dinamize, trigger a web push notification via Webpushr.
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.
Webpushr Explore Webpushr →
TriggersFires when a new alert or notification is created in Webpushr.
Fires when someone acknowledges an alert in Webpushr.
Sends a push notification through Webpushr.
Sends an SMS or voice notification via Webpushr.
Schedules a reminder notification in Webpushr.
Dinamize Explore Dinamize →
TriggersFires when a new subscriber is added in Dinamize.
Fires when a contact unsubscribes in Dinamize.
Fires when a subscriber opens or clicks a campaign in Dinamize.
Creates or updates a subscriber in Dinamize.
Unsubscribes a contact in Dinamize.
Adds a subscriber to a list or segment in Dinamize.
Sends a one-off transactional email via Dinamize.
Common questions
Can Knit build “When something happens in Dinamize, sync it to Webpushr.” between Webpushr and Dinamize?
Yes — describe it in the box above and Knit's Integrations Agent researches Webpushr and Dinamize'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.