When get system events in Addigy, sync it to Stripe.
When system events trigger in Addigy, record device metric events against customer profiles in Stripe.
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.
Addigy Explore Addigy →
TriggersFires when a device connected to Addigy comes online.
Fires when a device connected to Addigy goes offline.
Fires when a reading from a device in Addigy crosses a set threshold.
Sends a control command to a device via Addigy.
Adds a new device to Addigy.
Records a sensor reading or event from Addigy.
Stripe Explore Stripe →
TriggersFires when a new customer is created in Stripe.
Fires when a subscription is canceled in Stripe.
Fires when a new invoice is generated in Stripe.
Fires when a payment attempt fails in Stripe.
Creates a new customer in Stripe.
Creates a new subscription in Stripe.
Cancels an existing subscription in Stripe.
Updates a customer's billing details in Stripe.
Common questions
Can Knit build “When get system events in Addigy, sync it to Stripe.” between Addigy and Stripe?
Yes — describe it in the box above and Knit's Integrations Agent researches Addigy and Stripe'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.