Egnyte Make integrationAutomate Egnyte with Make.

Add a User to a Group places an existing Egnyte user inside a group, so team membership in Egnyte follows what your other tools already know.

Change a Task Status moves an Egnyte task forward without anyone opening the file, which keeps the task list accurate when the real work happens in another tool.

After you request an audit report, Check Audit Report Generation Status tells your scenario whether Egnyte has finished preparing it.

Copy File leaves the original in place and puts a duplicate in another folder, handy when two teams each need the same document in their own space.

Copy Folder duplicates a whole folder, which turns a well-built template into a ready structure for every new project or client.

Create a Bookmark bookmarks an Egnyte folder, so the right place is one click away the next time someone opens Egnyte.

Create a Comment writes a comment on an Egnyte file, putting context where people read the document instead of in a separate email thread.

Create a File Audit Report asks Egnyte to prepare a report on file activity, the first step whenever compliance wants a trace it can file away.

Create a File Link turns an Egnyte file into a public link you can send to anyone, a quick way to deliver a document to a client or a supplier.

Create a Folder adds a new folder in Egnyte, so each deal, hire or ticket gets its own tidy space without anyone clicking through the tree.

With Create a Folder Link, a whole Egnyte folder becomes a public link, so a partner opens every file inside from a single address.

Create a Group sets up a new Egnyte group, the building block for handling a whole team in one move rather than person by person.

Create a Group Provisioning Audit Report requests the group provisioning audit from Egnyte, the report IT reaches for when an auditor questions how teams are organized.

Create a Metadata Key adds a new custom field to an existing namespace, which is the Egnyte name for a set of custom metadata fields.

Create a Namespace defines a fresh set of custom metadata fields for your Egnyte domain, so files and folders can carry the labels your business really uses.

Create a Permission Audit Report starts a report on permissions, a clean way to answer “who can open what” without clicking through every folder.

Create a Task gives an Egnyte user a task tied to a file, so a review or an approval sits right next to the document concerned.

Create a User opens an Egnyte account for a new person, removing one manual step from every onboarding.

Create a User Provisioning Audit Report asks Egnyte for the user provisioning audit of your domain, useful when security wants a trail of the accounts on file.

Delete a Bookmark removes one bookmark, keeping Egnyte shortcuts in line with the projects that are still active.

Delete a Comment takes a specific comment off an Egnyte file, useful for cleaning up automated notes that are no longer true.

Delete a File removes a file from Egnyte inside your scenario, the clean-up step once a document has been copied, archived or replaced.

Delete a Folder removes an entire Egnyte folder, which is how a scenario closes a temporary workspace for good.

Delete a Group removes a group from Egnyte, keeping the group list aligned with how the company is really organized.

Delete a Link cuts a shared link, so the file or folder behind it can no longer be reached through that address.

Delete a Metadata Key removes one custom field from a namespace, the tidy-up move when a field no longer serves your process.

Delete a Namespace removes a whole set of custom metadata fields from your domain, a heavier move than deleting a single key.

Delete an Audit Report removes a report you no longer need, which keeps the list of generated reports short and easy to scan.

Delete a Task clears a task from Egnyte, the right call when the work it described was cancelled rather than done.

Delete a User removes a person from Egnyte, the closing step of an offboarding that should not depend on someone remembering it.

Delete Items from Trash wipes chosen files, folders or versions out of the Egnyte trash for good, up to 10 items each time the module runs.

Download File brings the content of an Egnyte file into your scenario, so the next module can attach it to an email, send it for signature or push it to another storage.

Get a Bookmark reads the details of one bookmark, so your scenario knows exactly what it points to before acting on it.

Get a Comment fetches one comment in full, handy when a later step needs exactly what was written on the file.

Get a Group shows who belongs to an Egnyte group, along with the group's attributes, a quick check on a team before you touch its access.

Get a Link returns the details of a shared link, so a scenario can check a link before sending it again or cutting it.

Get a Namespace lists every custom metadata key defined in a namespace, the reference to check before writing values on files.

Get a Task pulls the details of one Egnyte task, so a scenario can react to where that task stands right now.

Get a User retrieves one Egnyte user, the lookup step that turns a person into data your next modules can reuse.

Get File's Info returns the details of one Egnyte file, so your scenario can decide what to do with it before downloading anything.

Shows who holds which permission on one Egnyte folder, so a scenario can read access rights before it shares or moves anything inside.

Returns the details Egnyte keeps about a single folder, handed to the next module as one bundle (one item passed along the scenario) you can map into any field.

Gives a single figure: how many items currently sit in the trash across your Egnyte domain. Handy as a quick health check without pulling the whole list.

Reads the custom metadata values stored on one file or folder for a chosen namespace (a named set of metadata keys in Egnyte), so the scenario can route the item by its tags.

Puts a lock on an Egnyte file from inside the scenario, which is useful when a document enters a step where nobody should touch it.

Opens any endpoint of the Egnyte API from your scenario while reusing the connection (your Egnyte account linked to Make once) you already created for the other modules.

Changes the settings of an existing Egnyte folder without recreating it, so a folder can switch behavior as the project behind it evolves.

Takes one file out of its current folder and drops it into another, which turns a folder into a simple status board: to process, processed, archived.

Relocates a whole folder, with everything in it, to a new place in your Egnyte tree in one operation (one run of one module, the unit Make counts).

Takes one user out of an Egnyte group, which removes the access that group membership gave them without deleting the account.

Gives an existing Egnyte group a new name while its members and permissions stay in place, so nothing has to be rebuilt.

Brings files, folders or versions back from the Egnyte trash, up to 10 items in a single call, so an accidental deletion can be undone by the scenario.

Writes new permission entries for users or groups on one folder, which lets the scenario grant access at the exact moment it becomes needed.

Stamps metadata values on a file or folder inside a chosen namespace, so later searches and filters can find it by those values.

Releases the lock on an Egnyte file so people can work on it again, closing the loop opened by Lock a File.

Edits an existing file task in Egnyte, so the task stays in line with what happens in your other tools.

Changes the profile of an existing Egnyte user from the scenario, keeping the account in step with your source of truth for people.

Adjusts the name or the scope of a custom metadata namespace for your domain, leaving its keys untouched.

Rewrites the key definitions of a namespace, meaning the custom metadata fields files and folders can carry in your domain.

Creates a file in Egnyte from data another module passes along, or updates it when it already exists, so documents produced elsewhere land in the right folder.

Asks Egnyte to build a report of logins on your domain; Make classes this module as a search, so it hands back what Egnyte returns as bundles.

Pulls the data of a file audit report that already exists, as bundles your scenario can filter, count or write to a spreadsheet.

Retrieves the rows of a group provisioning audit, in other words the trace of group changes, so they can be archived outside Egnyte.

Returns the login report data Egnyte generated, one bundle per entry, ready to be sorted or sent where your security team works.

Reads the content of a permission audit report so you can review who received access to what, outside the Egnyte admin console.

Delivers the data of a user provisioning audit: the record of accounts added, changed or removed, turned into bundles Make can route.

Brings back every bookmark of the user behind the connection, which gives a scenario the list of folders that person follows.

Gathers the comments left on a file; an administrator can also call it with no parameter to get every comment across the domain.

Fetches Egnyte events on demand, as opposed to Watch Events, which waits for new ones; this is the module for looking back.

Opens one folder and returns its content, files and subfolders alike, each as its own bundle for the next module.

Returns all the groups of your Egnyte domain, which is the starting point for any scenario that audits or syncs team access.

Collects the links created in Egnyte for your account, the public links to files and folders included, so they can be reviewed in one place.

Shows every custom metadata namespace defined in your domain, so a builder can see what metadata exists before writing any.

Returns the files the connected user worked on recently, a quick way to rebuild a personal activity feed outside Egnyte.

Pulls the tasks of a given file, or every task the connected user created or received, depending on what you ask.

Lists what sits in the Egnyte trash of your domain, item by item, so a scenario can decide what to restore and what to purge.

Retrieves the users of your domain, all of them or a chosen subset, and returns one bundle per person.

Looks through your Egnyte content by file name, metadata or the text inside documents, and returns every match it finds.

Finds items that carry a given metadata field, or items whose field holds a specific value, which is how tagged content becomes queryable.