When new flic press in Flic, sync it to AWS Lambda.
When a Flic button is pressed, invoke an AWS Lambda function with the payload.
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.
AWS Lambda Explore AWS Lambda →
TriggersFires when a job, build or file conversion finishes in AWS Lambda.
Fires when a job, build or API request fails in AWS Lambda.
Calls an AWS Lambda endpoint with data from an earlier step.
Creates a PDF, image or converted file with AWS Lambda.
Checks or enriches a phone number, address or IP with AWS Lambda.
Flic Explore Flic →
TriggersFires when a device connected to Flic comes online.
Fires when a device connected to Flic goes offline.
Fires when a reading from a device in Flic crosses a set threshold.
Sends a control command to a device via Flic.
Adds a new device to Flic.
Records a sensor reading or event from Flic.
Common questions
Can Knit build “When new flic press in Flic, sync it to AWS Lambda.” between AWS Lambda and Flic?
Yes — describe it in the box above and Knit's Integrations Agent researches AWS Lambda and Flic'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.