Resources · Make integration

SigParser Make integrationAutomate SigParser with Make.

Want your SigParser contacts and companies to reach the rest of your tools on their own? The SigParser Make integration gives you 8 modules: 4 triggers and 4 actions. This page shows how to link your account, build a first scenario and pick the right module.

Try the SigParser integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SigParser Make integration do for you?

The SigParser Make integration links your SigParser account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: it watches SigParser for companies, contacts, emails or meetings, or it creates and looks up records for you.

Feed your CRM without copy and paste. Watch Contacts picks up the contacts SigParser holds and passes each one to the next module as a bundle (one item moving through the scenario), ready to land in a spreadsheet or a sales tool.

Keep SigParser complete when leads arrive elsewhere. A signup form or a chat tool can end with Create Contact or Create Company, so a new person or account shows up in SigParser without anyone typing it.

Check before you write. Get Contact by Email looks up one contact from an address, handy before you send a message or open a deal.

A few honest limits. The 4 triggers are scheduled: Make polls SigParser on the scenario's clock, and none of them is instant. The list has no update or delete module, and Make's documentation for SigParser is marked as limited, so test each module with a real run. When a listed module falls short, Make an API Call reaches the rest of the SigParser API with the same connection. If you are still weighing platforms, read the n8n vs Make comparison, and check Make pricing before you scale. New to the editor? The Make training starts from zero.

Connect

How do you connect SigParser to Make?

  1. 01

    Add a SigParser module

    Open a scenario, click the +, search for SigParser and pick any module, Watch Contacts for instance. In the module window, click Create a connection. A connection is your SigParser account linked to Make once, then reused by every SigParser module.

  2. 02

    Name it, then authorize

    Give the connection a name if you want to tell accounts apart later, a work and a test account for example. Then follow what SigParser asks: either approve Make on the SigParser page that opens, or paste the key SigParser gives you.

  3. 03

    Save and check

    Click Save. The connection now appears in the dropdown of every SigParser module, so the next ones you add need no new login. If the module fields stay empty, the connection is the first thing to check.

First scenario

Your first scenario: send new leads into SigParser

GoalWhen a new lead arrives in another app, such as a signup form, Make creates the contact in SigParser.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. This first module is the app where your leads come in, the form tool your site already uses.

  2. 02

    Set up the starting app

    Pick that app's trigger, click Create a connection to link its account, then choose the form or list Make should read. Make shows what it can see once the connection exists.

  3. 03

    Add Create Contact

    Click the + on the right of the first module, search for SigParser and pick Create Contact. Select your SigParser connection, then map the details the form collected into the fields Make displays.

  4. 04

    Test with Run once

    Send a test entry through your form, then click Run once. Open the bundles each module received and confirm the new contact really shows up in SigParser before going further.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Keep it or pick another, then switch the scenario on.

Triggers

What can start a SigParser scenario?

4 modules start a scenario when something happens in SigParser. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SigParser as soon as it happens.

SigParser1Watch Companies

Watch Companies

triggerIn the docs only

Watch Companies brings the companies SigParser finds into your scenario, one bundle per company, so the following module can file each account where your team tracks it.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, rather than hearing from SigParser the moment a company appears.
When to use it
choose it when the account is what matters to you, for example to open a folder or a record per company in another tool.
Watch out
the documentation gives no description of this trigger, so run the scenario once and read the bundles before you map anything.
SigParser2Watch Contacts

Watch Contacts

triggerIn the docs only

People are the point here: Watch Contacts sends each SigParser contact down your scenario as its own bundle, ready for a spreadsheet, a mailing list or a sales tool.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up what it finds at each check, so contacts arrive in batches, not one second after they appear.
When to use it
this is the natural start when you want new people in SigParser copied to the tool your sales team lives in.
Watch out
each contact that goes through a module costs an operation (one module run on one bundle), so a large first batch counts too.
SigParser3Watch Emails

Watch Emails

triggerIn the docs only

With Watch Emails, the emails SigParser has on record become the starting point of a scenario, each one passed along as a separate bundle you can route or log.

How it fires
scheduled. Make checks the app on the scenario's schedule, so an email waits for the next check before your scenario sees it.
When to use it
pick it when the message itself is the event you care about, say to keep a log of exchanges next to the customer file.
Watch out
Make's documentation does not describe what an email bundle contains, so click Run once and look at the real output before you build the next module on top of it.
SigParser4Watch Meetings

Watch Meetings

triggerIn the docs only

Meetings recorded in SigParser can drive a scenario too: Watch Meetings passes each one to the next module, useful for follow-ups that should not depend on someone's memory.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default and never faster than the interval your plan allows.
When to use it
reach for it when a meeting should trigger work elsewhere, such as a task for the account owner or a line in a shared sheet.
Watch out
no official description exists for this module, so test it with Run once and check which meetings actually come through before you switch the scenario on.
Modules

What can Make do in SigParser?

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

SigParser1

Create Company

ActionIn the docs only

Create Company adds a new account to SigParser from data another app already holds, so the company exists before anyone opens SigParser.

When to use it
after a deal is signed or a partner form is sent, when the organization matters more than a single person.
Watch out
the list has no update module, so a company created twice stays twice; check your source before you let the scenario run.
SigParser2

Create Contact

ActionIn the docs only

You get a new person in SigParser without typing a thing: Create Contact takes the details mapped from the previous module and records them as a contact.

When to use it
at the end of a lead flow, when someone fills in a form or books a demo in another tool.
Watch out
nothing here removes a mistake afterwards, since no delete module exists, so test with Run once on a single entry first.
SigParser3

Get Contact by Email

ActionIn the docs only

Give it an email address and Get Contact by Email returns the matching SigParser contact, so later modules can reuse what SigParser already knows about that person.

When to use it
before you write to someone or create a record, to work from the existing contact instead of starting blank.
Watch out
an address with no match gives the next module nothing to work with; run a test with an unknown address to see how your scenario behaves.
SigParser4

Make an API Call

ActionIn the docs only

This is the way out when the 7 other modules do not cover your need: Make an API Call reaches any endpoint of the SigParser API with the connection you already set up.

When to use it
when you need something no listed module does, such as changing or removing a record, provided the SigParser API offers it.
Watch out
you need the SigParser API documentation to know which endpoint to call, since Make gives no guidance for it on this app.
Need help

Need help automating SigParser with Make?

A person reads every message.

FAQ

Common questions about SigParser and Make

01Is the SigParser Make integration free?
Yes. SigParser is a standard app in Make, available from the Free plan, so you can build and test your scenarios without paying Make. The Free plan has limits you will feel: 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) drop the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. This page says nothing about the price of SigParser itself.
02What do you need to connect SigParser to Make?
A SigParser account and a Make account are enough to start. Make's documentation lists no prerequisite and no official connection steps for SigParser, so the generic Make flow applies: add a SigParser module, click Create a connection, name it if you like, then either approve Make on the SigParser page or paste the key SigParser gives you, and click Save. The connection is then shared by every SigParser module in your scenarios. If a module shows no data afterwards, open the connection again and check it before looking elsewhere.
03Do SigParser triggers in Make fire in real time?
No. All 4 SigParser triggers (Watch Companies, Watch Contacts, Watch Emails and Watch Meetings) are scheduled, and none is instant. Make checks SigParser on the scenario's schedule, every 15 minutes by default on a new scenario. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. So a new contact or meeting waits for the next check before your scenario handles it. For most follow-up work that delay is fine, but plan around it if a step must happen right away.
04What if a SigParser module is missing in Make?
Use Make an API Call. SigParser has it, and it can reach any endpoint of the SigParser API with the connection you already created, which can cover what the 8 listed modules leave out, such as changing or removing records if the SigParser API allows it. You will need SigParser's API documentation to pick the right endpoint, because Make's own documentation for this app is marked as limited. Test each call with Run once and read the returned bundle before you connect anything after it.
05Should you use Make or n8n for SigParser?
It depends on where your team already builds. On Make, SigParser comes with 4 scheduled triggers, 4 actions including Make an API Call, and a free start on the Free plan, which is often enough to try an idea on real data. The same app may also have an n8n node, so check both catalogs for the modules you need before deciding. The real criteria are the tool your team knows, the modules each platform offers for SigParser and how you want to run your automations, not a ranking between the two.
Same platform

Other docs you might need on this stack.

Browse all integrations