Organize file storage for newly created engineering issues

When a new issue is captured in Aspose, automatically create a dedicated folder in Brick FTP for team attachments and screenshots.

Try:

See all Brick FTP + Aspose integrations or talk to a human

Trusted by teams already building on Knit·

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.

Brick FTP Explore Brick FTP →

Triggers

New file uploaded

Fires when a new file is uploaded to Brick FTP.

File shared

Fires when a file in Brick FTP is shared with someone new.

Folder updated

Fires when a folder's contents change in Brick FTP.

Actions

Upload file

Uploads a file to Brick FTP.

Create folder

Creates a new folder in Brick FTP.

Share file

Shares a file from Brick FTP with a link or user.

Aspose Explore Aspose →

Triggers

Job completed

Fires when a job, build or file conversion finishes in Aspose.

Job failed

Fires when a job, build or API request fails in Aspose.

Actions

Run an API request

Calls an Aspose endpoint with data from an earlier step.

Generate or convert a file

Creates a PDF, image or converted file with Aspose.

Validate or look up a value

Checks or enriches a phone number, address or IP with Aspose.

Archive build files when a deployment is logged When a new deployment is tracked in Aspose, automatically upload the build report and release artifacts to Brick FTP. See details

Convert uploaded crash reports into developer issues When a crash dump or error log file is uploaded to Brick FTP, automatically create a new tracking issue in Aspose for engineering review. See details

See all Brick FTP + Aspose integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Organize file storage for newly created engineering issues” between Brick FTP and Aspose?

Yes — describe it in the box above and Knit's Integrations Agent researches Brick FTP and Aspose'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.

Why integrate Aspose with Brick FTP?

Connecting these apps ensures that logs, design specs, and build artifacts uploaded to Brick FTP instantly generate tracking items in Aspose.

Can deployment reports from Aspose be archived automatically in Brick FTP?

Yes, whenever a new deployment is tracked in Aspose, documentation can be saved and shared directly within Brick FTP.