Open issues from app requests
When a new request record is created in Adalo, create an issue in EasyCSV.
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.
Adalo Explore Adalo →
TriggersFires when a new record is added to an app built in Adalo.
Fires when a record changes in an Adalo app.
Fires when a record is deleted in an Adalo app.
Adds a new record to an app built in Adalo.
Updates an existing record in an Adalo app.
Removes a record from an Adalo app.
EasyCSV Explore EasyCSV →
TriggersFires when a job, build or file conversion finishes in EasyCSV.
Fires when a job, build or API request fails in EasyCSV.
Calls an EasyCSV endpoint with data from an earlier step.
Creates a PDF, image or converted file with EasyCSV.
Checks or enriches a phone number, address or IP with EasyCSV.
More Adalo + EasyCSV workflows
See all Adalo + EasyCSV integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Open issues from app requests” between Adalo and EasyCSV?
Yes — describe it in the box above and Knit's Integrations Agent researches Adalo and EasyCSV'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 a record in Adalo create an issue in EasyCSV?
Yes. When a record such as a bug report or request is created in Adalo, EasyCSV can open an issue or run a workflow.
Can developer events update my app?
When an issue closes or a deploy finishes in EasyCSV, the related record in Adalo can be updated automatically.