When get system events in Addigy, sync it to CloudBlue Connect.
When system events trigger in Addigy, sync the event logs to CloudBlue Connect.
See all Addigy + CloudBlue Connect 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.
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.
CloudBlue Connect Explore CloudBlue Connect →
TriggersFires when a customer places a new order in CloudBlue Connect.
Fires when an order in CloudBlue Connect is paid, fulfilled, refunded or disputed.
Fires when a new customer account is created in CloudBlue Connect.
Fires when a customer abandons their cart before completing checkout in CloudBlue Connect.
Creates or updates a product or listing in CloudBlue Connect.
Updates an order's status or fulfillment details in CloudBlue Connect.
Sends a custom API request to CloudBlue Connect for actions not covered by a dedicated action.
Common questions
Can Knit build “When get system events in Addigy, sync it to CloudBlue Connect.” between Addigy and CloudBlue Connect?
Yes — describe it in the box above and Knit's Integrations Agent researches Addigy and CloudBlue Connect'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.