Log issues in a sheet
When a new issue is opened in AWS Lambda, add a row to Data Blaze.
See all Data Blaze + AWS Lambda integrations or talk to a human
Google for Startups AcceleratorHow 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.
Data Blaze Explore Data Blaze →
TriggersFires when a row is added to a sheet in Data Blaze.
Fires when a row or column changes in Data Blaze.
Fires when a new spreadsheet or worksheet is created in Data Blaze.
Adds a new row to a sheet in Data Blaze.
Updates the values in an existing row in Data Blaze.
Finds a row by a column value in Data Blaze.
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.
More Data Blaze + AWS Lambda workflows
See all Data Blaze + AWS Lambda integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Log issues in a sheet” between Data Blaze and AWS Lambda?
Yes — describe it in the box above and Knit's Integrations Agent researches Data Blaze and AWS Lambda'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.
Can issues be logged in a spreadsheet?
Yes. New or updated issues in AWS Lambda can be added as rows in Data Blaze for reporting.
Can a row create an issue?
When a row is added in Data Blaze, AWS Lambda can open an issue with its details.