Archive files for closed records
When a record is deleted or closed in Backendless, move its files to an archive folder in Collect.
See all Collect + Backendless 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.
Collect Explore Collect →
TriggersFires when a new file is uploaded to Collect.
Fires when a file in Collect is shared with someone new.
Fires when a folder's contents change in Collect.
Uploads a file to Collect.
Creates a new folder in Collect.
Shares a file from Collect with a link or user.
Backendless Explore Backendless →
TriggersFires when a new record is added to an app built in Backendless.
Fires when a record changes in an Backendless app.
Fires when a record is deleted in an Backendless app.
Adds a new record to an app built in Backendless.
Updates an existing record in an Backendless app.
Removes a record from an Backendless app.
More Collect + Backendless workflows
See all Collect + Backendless integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Archive files for closed records” between Collect and Backendless?
Yes — describe it in the box above and Knit's Integrations Agent researches Collect and Backendless'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 new file create a record?
Yes. When a file is added to a folder in Collect, Backendless can create a record with the file name and link.
Can records create folders?
When a record is created in Backendless, Collect can create a folder for its documents.