Resources · Make integration

ComIDP Make integrationAutomate ComIDP with Make.

Can Make send your documents to ComIDP and bring the extracted data back? Yes. The ComIDP Make integration gives you 11 action modules, from file upload to text, table and stamp extraction. This guide shows how to connect your account and build a first scenario without code.

Try the ComIDP integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ComIDP Make integration do for you?

The ComIDP Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) hand a document to ComIDP and pass the result on to your other apps. All 11 ComIDP modules are actions: they act when the scenario reaches them, so something else has to start the flow.

Turn scanned paperwork into rows. A file lands in your storage app, Upload a File sends it to ComIDP, and Extract Tables Intelligently - CreateTask asks for its tables. The next module can write what comes back into a sheet or a database.

Clean up photos before reading them. Phone pictures of receipts are often skewed or dark. Correct an Image Distortion - Create a Task and Enhace Images Intelligently - Create a Task are named for exactly that job, and Intelligent Text Extraction - CreateTask can follow them.

Check that a contract carries its stamp. A legal or procurement team can send signed documents to Extract Stamp Intelligently - Create a Task and route the ones without a stamp to a person for review.

Know the limit before you start: Make itself says its documentation for ComIDP is incomplete, because little public information exists about the app. Field names and output formats are visible only once you open a module with a working connection. For a wider view of the platform, read the Make review, and if you are still choosing a tool, the n8n vs Make comparison lays out the criteria. When a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect ComIDP to Make?

  1. 01

    Add a ComIDP module

    In your scenario, click the +, type ComIDP in the search box and pick any of its modules, Upload a File for example. Make then asks for a connection: your ComIDP account linked to Make once, then reused by every ComIDP module.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps when a colleague or a test account also connects. Something like the account owner and the purpose is enough to tell them apart later.

  3. 03

    Authorize and save

    Depending on what ComIDP asks, either approve Make on the ComIDP page that opens, or paste the key ComIDP gives you into the field. Then click Save. The module now shows the connection name, and you can fill its fields.

First scenario

Your first scenario with ComIDP

GoalWhen a new document arrives in another app, Make uploads it to ComIDP and asks for its text.

  1. 01

    Create the scenario

    Open the Scenarios page, click to create a new scenario, then click the big +. The first module has to come from another app, since ComIDP has no trigger: your mailbox or file storage, for instance.

  2. 02

    Pick the source of the document

    Choose the module of that other app that hands over a file, connect its account and fill its fields. Make lists the folders or mailboxes it can read once the connection exists.

  3. 03

    Send the file to ComIDP

    Click the + on the right of the first module and add ComIDP Upload a File. Create the connection, then map the file coming from the previous module into the upload fields.

  4. 04

    Ask for the text

    Add Intelligent Text Extraction - CreateTask after the upload and map what the upload returned. Each module run on one bundle (one item passing through, here one file) counts as one operation on your Make plan.

  5. 05

    Test with Run once

    Drop a sample document where the first module looks, then click Run once. Open the bubble above each module to read the bundles it received and check what ComIDP sent back.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From there Make runs the chain on its own.

Modules

What each ComIDP module does

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

ComIDP1

AI Document Extraction

ActionIn the docs only

Hands a document to ComIDP and brings back the data its AI pulls out, ready for the next module to use. It is the broadest reader in the list.

When to use it
a mixed pile of invoices and forms where you want structured data without picking a specialised module first.
Watch out
the Make documentation does not list which fields come back, so run it once on a real file and read the output before mapping anything.
ComIDP2

Correct an Image Distortion - Create a Task

ActionIn the docs only

Gets a crooked photo straightened by ComIDP, so later reading steps work on a clean page. As the name says, it creates a ComIDP task for that correction.

When to use it
documents snapped with a phone at an angle, such as delivery notes signed on a counter.
Watch out
Make does not document what the task returns, so test with Run once to see whether you get a file or a task reference to pass on.
ComIDP3

Enhace Images Intelligently - Create a Task

ActionIn the docs only

Asks ComIDP to improve a poor image before anything reads it, which gives the extraction modules a better starting point. The module name keeps the typo Enhace, so search for it that way.

When to use it
faded faxes, dark scans or low-light receipts that come out unreadable.
Watch out
each module run is one operation, so place it only on the branch of files that really need it.
ComIDP4

Extract Stamp Intelligently - Create a Task

ActionIn the docs only

Looks for the stamp on a document and returns what ComIDP finds, so a scenario can react to a stamped or unstamped page. Its name marks it as a task creation step.

When to use it
official paperwork, customs forms or signed contracts where the stamp proves validity.
Watch out
the output format is not documented in Make, so add a filter only after reading a real result from Run once.
ComIDP5

Extract Tables Intelligently - CreateTask

ActionIn the docs only

Pulls the tables out of a document, the part people usually retype by hand, so the rows can move into a sheet or a database further down the scenario.

When to use it
price lists, bank statements or order forms whose value sits in a grid rather than in paragraphs.
Watch out
a table can come back as several items, so check in the test run whether you need an iterator before writing rows.
ComIDP6

Get the File Information

ActionIn the docs only

Reads back what ComIDP knows about a file you already sent, which lets the scenario confirm the upload before spending more operations on it.

When to use it
right after Upload a File, when you want a checkpoint before launching an extraction.
Watch out
Make lists no fields for this module, so open it with a live connection to see which details ComIDP actually returns.
ComIDP7

Intelligent Text Extraction - CreateTask

ActionIn the docs only

Turns the words on a scanned page into text your other apps can search, store or send. It is the natural pick when you care about the prose, not the tables.

When to use it
letters, reports or scanned mail you want searchable in your document system or pasted into a ticket.
Watch out
if the source is a skewed photo, place the distortion correction module in front of it first.
ComIDP8

Make an API Call

ActionIn the docs only

Calls any endpoint of the ComIDP API from your scenario with the same connection, which covers whatever the ten other modules leave out.

When to use it
you found an operation in the ComIDP API documentation that no listed module offers.
Watch out
you write the request path and body yourself, so keep the ComIDP API reference open while you build it and test with Run once.
ComIDP9

Parse Intelligent Document - Create a Task

ActionIn the docs only

Asks ComIDP to break a whole document into its parts rather than grabbing only text or only tables. Going by the name, it opens a parsing task on the file.

When to use it
structured forms such as applications or claims, where you need several sections from the same page.
Watch out
Make does not say how the parts are returned, so map the result only after a real test run.
ComIDP10

Start a Task

ActionIn the docs only

Starts a ComIDP task from the scenario. The name points to a companion for the modules ending in Create a Task, which would set a job up without launching it.

When to use it
when a test run shows that a created task sits waiting instead of producing a result.
Watch out
this pairing is read from the module names, not confirmed by the Make documentation, so check it on a real file first.
ComIDP11

Upload a File

ActionIn the docs only

Sends a file from an earlier module to ComIDP, the step that usually opens any ComIDP chain in a scenario. Without it the other modules have nothing to read.

When to use it
an attachment from email, a file from cloud storage or a form upload that needs processing.
Watch out
on the Make Free plan files are capped at 5 MB, so large scans can stop the run before ComIDP sees them.
Need help

Need help automating ComIDP with Make?

A person reads every message.

FAQ

ComIDP and Make: common questions

01Is the ComIDP Make integration free?
Yes, on the Make side. ComIDP is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Every module run counts as one operation against your monthly credits. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your ComIDP account and its own pricing are a separate matter this page does not cover.
02What do you need to connect ComIDP to Make?
A ComIDP account and a Make account. Make gives no official prerequisite for ComIDP, so the generic connection flow applies: add any ComIDP module, click Create a connection, name it if you like, then approve access on the ComIDP page or paste the key ComIDP gives you, and click Save. The connection is stored once and reused by all 11 modules. Since the ComIDP documentation in Make is marked as limited, keep your ComIDP account open to find the key if one is asked.
03Can ComIDP start a Make scenario on its own?
No. ComIDP has no trigger module in Make, only 11 actions. The scenario has to start elsewhere. The first option is a trigger from another app, such as a new email attachment or a new file in cloud storage, followed by the ComIDP modules. The second is Make's own schedule on the first module, every 15 minutes by default and down to 1 minute on paid plans. Whatever starts it, click Run once to test the chain one time and read what each module received before you switch the scenario on.
04What if a ComIDP feature is missing from Make?
Use the Make an API Call module. It reaches any endpoint of the ComIDP API with the connection you already created, so an operation that none of the 10 other modules offers stays within reach. You write the request yourself, which means reading the ComIDP API reference. Also know that Make describes its ComIDP documentation as limited for lack of public information, so test each module with Run once and read the output before mapping it further down the scenario.
05Should you use Make or n8n for ComIDP?
It depends on the tool you already run. On Make, ComIDP has 11 ready modules, a Make an API Call module for the rest, and it works from the Free plan. The same app often has an n8n node too, so check that before choosing. The deciding criteria are where your other automations already live, who on the team will maintain them, and which editor they find easier to read.
Same platform

Other docs you might need on this stack.

Browse all integrations