Resources · Make integration

Bitskout Make integrationAutomate Bitskout with Make.

Turn documents into clean data without typing a single field. The Bitskout Make integration gives you 14 action modules that read invoices, receipts, CVs and more. This page shows you how to connect Bitskout, then walks you through a first scenario.

Try the Bitskout integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Bitskout Make integration automate?

The Bitskout Make integration lets a Make scenario (the automation you build, a chain of steps) send a document or a text to Bitskout and get structured data back. Each step is a module: here, all 14 are actions, so the scenario starts on another app or on a schedule, then hands the file to Bitskout.

Supplier bills that fill your books. An accounting team drops PDFs into a shared folder; Extract data from Invoices pulls out the details and the next module writes them into a spreadsheet or an accounting tool. Paper expense slips follow the same path with Extract data from Receipts.

A hiring pipeline that sorts itself. A recruiter receives applications by email. Extract data from CV (Resume) turns each attachment into a candidate profile, ready to land in an applicant tracker. For a trade show, Extract data from Business Cards does the same with scanned cards.

Mixed inboxes routed to the right place. When one mailbox receives purchase orders, bills of lading and invoices side by side, Detect Document Type tells them apart first, and a router sends each one to the matching extraction module.

What the page cannot promise: Make's own documentation for Bitskout warns that it was written with AI help and may contain mistakes, so check anything critical with Bitskout. The module list does not describe the fields each one returns; a test run shows them. If you are still choosing a tool, our n8n vs Make comparison lays out the criteria, and the Make training covers routers and mapping from scratch.

Connect

How do you connect Bitskout to Make?

  1. 01

    Generate an API key in Bitskout

    You need an active Bitskout account. Open Settings, then API Keys, click the button that generates a key and copy the key shown on screen. Keep it at hand, Make asks for it in the next step.

  2. 02

    Add a Bitskout module and open the connection

    In your scenario, add any Bitskout module and click Create a connection. A connection is your Bitskout account linked to Make once; every Bitskout module in your scenarios reuses it.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the instructions on screen, and save.

First scenario

Your first scenario with Bitskout and Make

GoalWhen a new invoice file reaches another app, Make asks Bitskout to confirm it is an invoice and extract its data.

  1. 01

    Create the scenario and pick your source

    From the Scenarios page, create a new scenario and click the +. Bitskout has no trigger, so the first module comes from the app where your files arrive, such as a storage or email app.

  2. 02

    Add Detect Document Type

    Click the + on the right, search Bitskout and pick Detect Document Type. Click Create a connection, paste your API key, then map the file coming from the first module.

  3. 03

    Chain Extract data from Invoices

    Add Extract data from Invoices after it, reuse the same connection and map the same file. Make offers the data of earlier modules in a panel, so you pick values rather than type them.

  4. 04

    Test with Run once

    Drop a sample invoice in your source and click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one file and its extracted data.

  5. 05

    Schedule and switch it on

    Open the clock on the first module: a new scenario checks every 15 minutes by default, and the Free plan cannot go below 15. Set the interval you need, then switch the scenario on.

Modules

What each Bitskout module does in Make

Bitskout gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Bitskout1

Detect Document Type

ActionIn the docs only

Sends a file to Bitskout and returns what kind of document it is, so one scenario can handle a mixed pile of paperwork without you sorting it by hand.

When to use it
a shared inbox where invoices, receipts and purchase orders all land together, and each needs a different extraction module.
Watch out
the documentation does not list which types it recognizes, so run a sample of each kind through Run once before you build routes on the result.
Bitskout2

Extract data from Bill of Lading

ActionIn the docs only

Reads a bill of lading and hands back its content as data you can map, which spares a logistics team from retyping shipment paperwork into their own tools.

When to use it
a carrier sends shipping documents by email and you want each one logged in a tracking sheet as soon as the scenario picks it up.
Watch out
the fields returned are not documented, so check the output bundle before mapping it downstream.
Bitskout3

Extract data from Business Cards

ActionIn the docs only

Turns a photo or scan of a business card into contact data, ready to become a lead in your CRM instead of a card lost in a drawer.

When to use it
after a trade show, when the sales team uploads card pictures to a shared folder and wants each contact created without typing.
Watch out
each card is one file and one operation, meaning one run of this module that Make counts on your plan.
Bitskout4

Extract data from CV (Resume)

ActionIn the docs only

Reads a resume and returns the candidate's details as structured data, so a recruiter gets comparable profiles instead of a folder of attachments in every layout.

When to use it
applications arrive by email or through a careers form, and you want each candidate added to your applicant tracker automatically.
Watch out
resumes hold personal data, so decide where the extracted profiles are stored before you switch the scenario on.
Bitskout5

Extract data from HARO Query

ActionIn the docs only

Pulls the useful parts out of a HARO journalist request, so a PR or content team can triage press opportunities in a table rather than reading every email in full.

When to use it
HARO queries land in a mailbox and you want each one logged with its key details for someone to pick the relevant ones.
Watch out
the documentation does not say whether it expects the email text or a file, so test both inputs with Run once.
Bitskout6

Extract data from Invoices

ActionIn the docs only

Reads a supplier invoice and gives back its details as mappable data, the step that removes manual entry from accounts payable.

When to use it
invoices reach a shared folder or inbox, and the next module writes them into your spreadsheet or accounting app for approval.
Watch out
if the same folder also receives receipts or orders, place Detect Document Type in front so each file goes to the right extractor.
Bitskout7

Extract data from Purchase Order

ActionIn the docs only

Converts a customer's purchase order into data, so sales operations can open an order in their own system without copying lines from a PDF.

When to use it
buyers email their orders as attachments and you want each one recorded where your team prepares deliveries.
Watch out
the returned fields are not listed in the documentation; read the bundle from a test run before mapping line details into another app.
Bitskout8

Extract data from Receipts

ActionIn the docs only

Reads a receipt, often a phone photo, and returns its details as data, which makes expense reports far less tedious for the people filing them.

When to use it
employees drop receipt pictures into a folder or chat, and you want each expense logged in a sheet for finance to review.
Watch out
pick this one rather than the invoice extractor for till slips; if both kinds arrive together, route them with Detect Document Type first.
Bitskout9

Make an API Call

ActionIn the docs only

Calls any endpoint of the Bitskout API from your scenario, using the connection you already set up, so you are not stuck when a listed module does not cover your case.

When to use it
you need a Bitskout feature that none of the other Bitskout modules exposes.
Watch out
you have to know the endpoint and what it expects; the Bitskout API documentation is the reference here, not the Make interface.
Bitskout10

Run Comparison (New)

ActionIn the docs only

Asks Bitskout to run a comparison, judging by the module name, and returns the result to your scenario. The Make documentation does not describe what is compared or how.

When to use it
you have already set up a comparison on the Bitskout side and want Make to run it on the documents your scenario collects.
Watch out
it sits next to Run Comparison Plugin with no documented difference, so test both with Run once.
Bitskout11

Run Comparison Plugin

ActionIn the docs only

Runs a Bitskout comparison plugin from Make, going by its name, and brings the output back as data for the next modules. Its settings and output are not documented on the Make side.

When to use it
a scenario built earlier already relies on it, or the Bitskout team pointed you to this version.
Watch out
before you pick it for a new scenario, compare its output with Run Comparison (New) on the same files.
Bitskout12

Run Plugin for a File

ActionIn the docs only

Sends a file to one of your Bitskout plugins, as the name indicates, and returns what the plugin produced. Useful when none of the ready-made extractors fits your document.

When to use it
you work with a document type that has no dedicated module, such as an internal form, and have configured a plugin for it in Bitskout.
Watch out
the documentation says nothing about how plugins are built; that part happens in Bitskout, not in Make.
Bitskout13

Run Plugin for a File (New)

ActionIn the docs only

A second version of the file plugin module, also sending a document to a Bitskout plugin and returning its result. The Make documentation does not explain how it differs from the original.

When to use it
you are starting a fresh scenario around a custom Bitskout plugin and want to compare both versions.
Watch out
run the same file through each one with Run once and keep the version whose output bundle suits your mapping.
Bitskout14

Run Plugin for a Text

ActionIn the docs only

Applies a Bitskout plugin to plain text instead of a file, so content already sitting in an email body or a form answer can be processed without creating a document.

When to use it
the information arrives as text, for example the body of a message mapped from an earlier module, and has no attachment.
Watch out
if your source is a PDF or an image, use one of the file modules: judging by its name, this one is built for text.
Need help

Need help automating Bitskout with Make?

A person reads every message.

FAQ

Questions about the Bitskout Make integration

01Is the Bitskout Make integration free?
Yes on the Make side: Bitskout is a standard app, available from the Free plan. That plan allows 2 active scenarios, scheduled runs no closer than 15 minutes apart, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Every module run is an operation counted in your monthly credits. Bitskout itself needs its own active account and subscription, which Make does not cover.
02What does connecting Bitskout to Make require?
An active Bitskout account and an API key from it. In Bitskout, go to Settings, then API Keys, generate a key and copy it. In Make, add any Bitskout module, click Create a connection, optionally give it a name in the Connection name field, and paste the key. That connection is then reused by every Bitskout module you add, in this scenario and the next ones, so the setup only happens once per account.
03Can a Bitskout scenario start on its own?
Not from Bitskout: all 14 modules are actions and none is a trigger. The scenario starts with a module from another app, for example a new file in a storage app or a new email with an attachment, and Bitskout comes right after. How fast it reacts depends on that first module and the scenario's schedule, which is every 15 minutes by default and at least 15 minutes on the Free plan. Set the clock on the first module to match your needs.
04What if a needed Bitskout module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Bitskout API with the connection you already created, so you can cover what the other modules do not. You will need the Bitskout API documentation to know the endpoint and what to send. Also keep in mind that Make's page on Bitskout is marked as AI-generated and may contain mistakes, so for anything that matters, confirm the behavior with Bitskout directly.
05Make or n8n: which fits Bitskout better?
It depends on how you prefer to build rather than on Bitskout. On Make you get 14 ready-made Bitskout modules, a visual editor where you test with Run once, and Make an API Call for the rest. Many apps also have an n8n node, so check whether Bitskout does before deciding. Compare the two on the criteria that matter to your team, such as the modules available for your other tools and how your team likes to work, rather than on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations