Log uploaded file metadata into a database

Whenever a new file is uploaded in ezidox, insert a row into SQL Server to track file paths, file sizes, and owner details.

Try:

See all ezidox + SQL Server 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.

ezidox Explore ezidox →

Triggers

New file uploaded

Fires when a new file is uploaded to ezidox.

File shared

Fires when a file in ezidox is shared with someone new.

Folder updated

Fires when a folder's contents change in ezidox.

Actions

Upload file

Uploads a file to ezidox.

Create folder

Creates a new folder in ezidox.

Share file

Shares a file from ezidox with a link or user.

SQL Server Explore SQL Server →

Triggers

New row inserted

Fires when a new row is added to a table in SQL Server.

Row updated

Fires when an existing row changes in SQL Server.

Query result ready

Fires when a scheduled query in SQL Server finishes running.

Actions

Run a query

Runs a SQL query against SQL Server and returns the result.

Insert or update a row

Writes a new or updated row to SQL Server.

Sync a table

Syncs a table in SQL Server with data from another source.

Create storage folders for new database entries When a new project record is inserted into SQL Server, automatically create a corresponding project directory in ezidox. See details

Track shared file activity in database logs When a file is shared in ezidox, update the corresponding permissions log row in SQL Server to keep security records current. See details

See all ezidox + SQL Server integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Log uploaded file metadata into a database” between ezidox and SQL Server?

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

What's the most common Databases & Warehouses + Files & Storage automation?

Writing file metadata (name, folder, uploader, timestamp) from ezidox into a table in SQL Server as files are added, for audit or usage reporting.

Does this sync the actual file contents, or just metadata?

By default just metadata — the Agent can also extract and sync structured content from a file (like a CSV) into SQL Server if that's what you need.