Skip to content

Integrations

FileOnion connects to the rest of your toolchain three ways: a native Dropbox integration, webhooks that push events to any HTTPS endpoint, and a REST API with scoped API keys. This page is for Owners and Admins setting up those connections.

Everything below lives in Settings → Integrations.

What's connectable today

The Applications Linked to Your Account table lists partner applications with their connection status and Add / Reset / Remove actions. Dropbox is currently the only application with an active connect flow — other listed applications cannot be connected yet. For Zapier, Make, n8n, and similar automation tools, use webhooks and API keys instead; they work today on any plan that includes automation integrations.

Dropbox

The Dropbox integration lets you copy files from your FileOnion File Manager into your Dropbox account. It's included on all plans.

Connect Dropbox

  1. Go to Settings → Integrations.
  2. In the applications table, click Add on the Dropbox row.
  3. You're taken to Dropbox to authorize FileOnion (standard OAuth — FileOnion never sees your Dropbox password).
  4. Approve, and you're returned to FileOnion.

Checkpoint

The Dropbox row now shows a Connected status chip.

Sync files to Dropbox

From the File Manager, open the menu on any file or folder and choose Sync to dropbox. FileOnion copies the file — or the folder's contents — to your connected Dropbox. If you haven't connected yet, choosing the action starts the Dropbox authorization flow first.

One-way, on demand

Sync is per-item and one-way (FileOnion → Dropbox), triggered when you choose the action. It is not a continuous two-way sync.

Disconnect

On the Dropbox row, click Remove and confirm. The confirmation warns: "If you proceed, all shared data will be removed from FileOnion." Use Reset if the connection is misbehaving and you want to re-establish it.

API keys

On the Professional plan and above, Settings → Integrations includes an API Keys card for the FileOnion REST API.

Click New API Key, give it a name (for example "Zapier Integration"), pick its scopes — Read, Write, Manage Clients, Manage Webhooks, or Full Access — and optionally set an expiration (30, 90, or 180 days, 1 year, or never).

Copy the key immediately

The full key is shown once, right after creation, with a Copy button. After that, only its prefix is visible. If you lose a key, revoke it and create a new one.

The table lists each key's prefix, scopes, status, creation date, last-used date, and expiry. Revoke disables a key immediately ("Any integrations using this key will stop working immediately"); Delete removes it permanently.

For endpoints, authentication, and request examples, see the API guide and the API reference.

Webhooks

Also on Professional and above, the Webhooks card lets FileOnion push real-time event notifications to your systems.

Click New Webhook and provide:

  • Endpoint URL — must be HTTPS.
  • Description (optional) — e.g., "Zapier — New request notifications".
  • Events — pick individual events or whole categories from the event picker.

Each webhook subscription then shows:

  • A status chip — Active, Paused, or Failed.
  • A Signing Secret (with Show/Copy) — use it to verify that deliveries genuinely came from FileOnion.
  • Test — sends a test delivery and reports the result (HTTP status and duration).
  • Pause / Resume, Edit (change URL, description, or events), and Delete.
  • Delivery health: last delivery time, last HTTP status, and a failure count.

Webhooks from workflows

Separately from these subscriptions, workflow stage automations include a Webhook Call action — useful when you want a webhook to fire only when a request moves through a specific stage, rather than on every event of a type.

Automation platforms (Zapier, Make, n8n)

There is no FileOnion app to install inside these platforms today. Instead, they connect through the generic webhook and API support above — which is exactly what they're built for:

  • Zapier — trigger Zaps with the "Webhooks by Zapier" trigger; point a FileOnion webhook subscription at the Zap's URL.
  • Make — use the HTTP module.
  • n8n — use the Webhook node.
  • Power Automate — use the HTTP connector.
  • Any other HTTP-capable tool works the same way.

The pattern:

  1. Create an API key (if the tool needs to call FileOnion back — to fetch details or take actions).
  2. Create a webhook subscription pointing at the URL your automation tool gives you, and select the events you care about.
  3. Build the automation in your tool, using the webhook payload as the trigger and the REST API for follow-up actions.
  • API guide — authentication, endpoints, and examples
  • Workflows — stage automations, including the Webhook Call action
  • File Manager — where the Dropbox sync action lives
  • Billing — which plans include API access and automation integrations