Resources · Make integration

Xelians Datahub Make integrationAutomate Xelians Datahub with Make.

Can Make push your documents into Xelians Datahub without a line of code? The Xelians Datahub Make integration gives you 3 action modules and no trigger. This guide is for teams that archive files, and it walks you from the connection to a first working scenario.

Try the Xelians Datahub integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Xelians Datahub Make integration do?

The Xelians Datahub Make integration links your Xelians Datahub account to Make so that another app, or a schedule, can hand work to Datahub for you. You build a scenario, which is the automation itself: a chain of modules, each one a small brick that does a single job. Here all three bricks are actions.

Files that land in Datahub on their own. Start the scenario from another app, such as a form tool or a cloud drive, then let Send a file carry each document to Datahub. Every file travels as a bundle, one item passed from module to module.

A process that starts without a click. Place Create a workflow after the step that matters in your other tool, so Datahub receives the request the moment the scenario reaches it.

Anything the menu leaves out. Make an API Call reuses your connection to reach any endpoint of the Datahub API, which covers what the two other modules do not.

Know the limits before you plan. Make's own documentation for this app is thin: it says there is not enough public information to describe it fully, so test each module with your own account. There is also no trigger, so another app or the schedule has to start things. If you are new to the editor, the Make training is a good first step, and the n8n vs Make comparison helps if you are still picking a tool.

Connect

How do you connect Xelians Datahub to Make?

  1. 01

    Add a Datahub module

    In your scenario, click the + and search for Xelians Datahub, then pick any of its modules. Make asks for a connection first: that is your Datahub account linked to Make once and reused by every Datahub module. Click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when you manage more than one account. Then authorize Make on the Datahub page that opens, or paste the key Datahub gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and any other Datahub module you add later can pick it from the list instead of asking you to sign in again.

First scenario

Build your first scenario with Xelians Datahub

GoalWhen a new file shows up in another app, Make sends it to Xelians Datahub.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Datahub has no trigger, pick the app where your files arrive first, such as a drive or a form tool.

  2. 02

    Set up the starting module

    Connect that app and fill its fields. Once the connection exists, Make lists the folders or objects it can read, so you choose from a menu instead of typing paths.

  3. 03

    Add Send a file

    Click the + on the right of the first module, search for Xelians Datahub and pick Send a file. Create the connection, then map the file coming from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received to confirm the file reached Datahub.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on it runs by itself, and each module run counts as one operation on your plan.

Modules

What can Make do in Xelians Datahub?

Xelians Datahub gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Xelians Datahub1

Create a workflow

ActionIn the docs only

Going by its name, this action starts a new workflow in Datahub from your scenario, so a process begins the moment an earlier step finishes rather than when someone remembers it.

When to use it
place it after the module that marks the real starting point, for example a signed form arriving in another app.
Watch out
Make has no official description for this module, so run it once on a test case and check the result in Datahub.
Xelians Datahub2

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the Datahub API while reusing the connection you already created, so you never manage a second login.

When to use it
pick it when neither Send a file nor Create a workflow covers the operation you need.
Watch out
you write the request yourself, which means reading the Datahub API documentation first; Make does not describe the endpoints for you.
Xelians Datahub3

Send a file

ActionIn the docs only

You get your documents into Datahub without uploading them by hand: the module takes a file handed over by an earlier module and delivers it to your account.

When to use it
right after the module that produces the file, such as a new attachment or an export from another tool.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size of heavy scans before you send them.
Need help

Need help automating Xelians Datahub with Make?

A person reads every message.

FAQ

Questions about the Xelians Datahub Make integration

01Is the Xelians Datahub Make integration free?
Yes, Xelians Datahub is a standard app, so its modules work on the Make Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Make counts usage in operations, one per module run on one bundle. Your Datahub subscription is a separate matter that Make does not cover.
02What is needed to connect Xelians Datahub to Make?
You need a Make account and access to a Xelians Datahub account. Make's documentation lists no specific prerequisite for this app. The generic steps apply: add a Datahub module, click Create a connection, name it if you want, authorize Make on the Datahub page or paste the key Datahub gives you, then click Save. The connection is stored once and every Datahub module in your scenarios can reuse it. If the authorization window asks for details you do not have, ask the administrator of your Datahub account.
03Does the Xelians Datahub Make integration have a real-time trigger?
No, the app has no trigger at all, scheduled or instant. Your scenario therefore has to start somewhere else. The usual way is a trigger from another app, for example a drive or a form tool, placed as the first module with the Datahub actions after it. You can also start the scenario on a schedule set on the first module, every 15 minutes by default, down to 1 minute on paid plans. Either way, Datahub receives work only when the scenario reaches its modules.
04What if a Xelians Datahub module is missing in Make?
It depends on what you need, but the Make an API Call module is the usual answer. It calls any endpoint of the Datahub API with the connection you already set up, so it covers operations that Send a file and Create a workflow do not. You will need the Datahub API documentation to write the request. Keep in mind that Make's own documentation for this app is limited, because there is not enough public information about it, so test each call with Run once before switching the scenario on.
05Make or n8n for Xelians Datahub?
It depends on the tool your team already uses. Many apps have an n8n node as well as Make modules, so check that Xelians Datahub is available where you plan to build. On Make, you get three action modules, including Make an API Call for anything else, a connection reused across modules and a visual editor with Run once for testing. Compare what each tool offers for this exact app, list the operations you need, and choose the one where they are all covered.
Same platform

Other docs you might need on this stack.

Browse all integrations