Resources · Zapier integration

LogicManager Zapier integrationAutomate LogicManager with Zapier.

The LogicManager Zapier integration gives you 3 triggers, 11 actions and 18 searches. One trigger is instant, two are checked on a timer, and LogicManager is not a premium app, so it runs on the free plan. Here is what each piece does and what it bills.

See the 32 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LogicManager Zapier integration does for your risk team

The LogicManager Zapier integration connects your risk register to the rest of your tools through Zaps: small automations that start on one event, then run one or more steps without anyone touching them. LogicManager handles enterprise risk work such as incidents, third parties and policies; Zapier carries its data in and out.

Three results come up most. Incidents opened from outside: another tool sends a request, Catch Webhook receives it and Create Event files it under the right event type. A register that keeps itself current: New or Updated Taxonomy Element spots a change and a row in your spreadsheet follows. Monitoring evidence logged in one place: Create Monitoring Activity Results writes completed result rows against a monitoring activity of a plan.

The tip that matters most: of the three triggers, only Catch Webhook is instant. It reacts at once, even on the free plan. The two others wait for the next check, and on the free plan that check comes every 15 minutes.

Now what Zapier does not do here. There is no delete action at all, for events, elements, documents or users. The two polling triggers only look at items created or updated in the last 24 hours, for one type at a time. And most searches want a numeric ID, not a name.

Still picking a tool? See our Zapier review and our Make vs Zapier comparison. Hack'celeration has no LogicManager page for Make or n8n yet.

Vocabulary

Zapier vocabulary, explained plainly

Seven words carry this whole page. Here they are, in plain English.

Zap
An automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app for you.
Task
The unit Zapier bills. One action that completes successfully counts as one task on your plan.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found.
Cost

What LogicManager costs you in Zapier tasks

The trigger is free, and so is every check Zapier runs to look for new items. You pay one task for each action that goes through. An action that fails is not counted.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger0 task
  • Each successful action1 task

The free plan gives 100 tasks a month and Zaps of two steps: one trigger, one action. A second action, a filter or a search turns the Zap into a multi-step Zap, which needs a paid plan. With 18 searches on offer, that line comes fast. The grid below sets how often the two polling triggers are checked; Catch Webhook is instant and ignores it. A few apps bill more than one task per action; nothing in the catalog says LogicManager does.

Connect

Connect LogicManager to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your LogicManager account linked once, then reused by every step that talks to LogicManager.

  2. 02

    Pick LogicManager

    Search for LogicManager in the dialog, select it and click Add connection. A new tab opens: sign in with the LogicManager account your Zaps should act as.

  3. 03

    Grant access

    Allow Zapier to use that account. Before building, check its rights: it needs read or write access on every event type, taxonomy and plan you do not own and want a Zap to touch.

First Zap

Your first Zap: turn an outside report into a LogicManager event

GoalEach time another tool posts a report to your Zapier address, open a matching event in LogicManager under the event type you choose.

  1. 01

    Build: set the trigger

    Create a Zap and pick LogicManager with the Catch Webhook event. Zapier generates an address; paste it into the tool that should report incidents.

  2. 02

    Send a test report

    Have that tool send one real report, then run the trigger test. You map the next step on what actually arrived, not on empty placeholders.

  3. 03

    Add Create Event

    Add a LogicManager action, Create Event, and choose the event type first. Its profile fields load next; map each one to a value from the report.

  4. 04

    Test the action

    Run the action test and open LogicManager to read the event it created. Two steps only, so this Zap fits the free plan and its 100 monthly tasks.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, each report the tool sends opens one event in LogicManager and uses one task.

Triggers

LogicManager triggers in Zapier

3 events start a Zap when something happens in LogicManager, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Catch Webhook

Instant trigger

In Zapier“Starts the Zap when Zapier receives an HTTP request at the generated webhook URL.”

Zapier hands you a dedicated address, and any request sent to it starts the Zap with whatever data came along. It is the open door for tools that have no LogicManager trigger of their own.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a reporting form or an alerting tool can post to an address, and each post should become a LogicManager event without anyone copying it.
Watch out
the trigger takes whatever lands on the address, so test with a real request before you map fields, or the next step has nothing to pick from.
2

New or Updated Event

Polling trigger

In Zapier“Trigger on events created or updated in the last 24 hours for the selected event type. Prefer the optional profile filter to narrow noisy event types.”

This trigger watches one event type and picks up events created or changed in the last 24 hours. An optional profile filter narrows it down when that type gets busy.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
every new or edited incident of one type should reach a shared spreadsheet or a team channel without a manual export.
Watch out
Event Type is required and expects the numeric ID of the type, so find it in LogicManager before you start building.
3

New or Updated Taxonomy Element

Polling trigger

In Zapier“Trigger on taxonomy elements created or updated in the last 24 hours for the selected taxonomy type. Prefer the optional profile filter to narrow noisy taxonomies.”

Pick a taxonomy family and the Zap starts on every element of it that was added or edited in the last 24 hours. A profile filter, optional, keeps a crowded taxonomy quiet.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
your list of vendors or risks lives in LogicManager and a copy elsewhere should follow each change.
Watch out
if a later step of the same Zap edits that taxonomy with Update Taxonomy Element by ID, the change shows up again at the next check and the Zap restarts itself.
Actions

LogicManager actions in Zapier

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

1

Create Event

Action

In Zapier“Create one LogicManager event in the selected event type. Dynamic profile fields load after event_type is chosen.”

Opens one new event under the event type you pick, with that type's own profile fields to fill.

When to use it
an incident reported through a form should land in LogicManager on its own.
Watch out
choose the type first; the profile fields only appear after it.
2

Create Event Document

Action

In Zapier“Upload one document to an event.”

Uploads one file to an existing event, so the evidence sits next to the incident it belongs to.

When to use it
a report arrives through a form and must be attached to an open event.
Watch out
you need both the Event Type ID and the Event ID, usually from an earlier step.
3

Create Monitoring Activity Results

Action

In Zapier“Create completed result rows for a monitoring activity. Provide results_json as a JSON array or an object with a results array.”

Writes completed result rows against a monitoring activity, inside the plan that owns it. Each result carries an as-of date.

When to use it
a control test runs in another tool and its outcome should be logged against the right activity.
Watch out
Plan ID, Monitoring Activity ID and Results JSON are all required, and the IDs are numeric.
4

Create Taxonomy Document

Action

In Zapier“Upload one document to a taxonomy element.”

Attaches one file to a taxonomy element, such as a contract or a certificate on a vendor record.

When to use it
a signed document saved in a shared folder should also sit on the element it concerns.
Watch out
Element Id is numeric and required; a search like Get Taxonomy Element by Id can supply it.
5

Create Taxonomy Element

Action

In Zapier“Create one taxonomy element in the selected taxonomy type. Dynamic profile fields load after taxonomy_type is chosen.”

Adds one element to a taxonomy type you select, under the Name you give it, then fills the profile fields of that type.

When to use it
a new third party approved elsewhere should appear in your LogicManager register.
Watch out
Taxonomy type and Name are both required; the Name is what the new element is called in your register.
6

Create Users

Action

In Zapier“Create one or more LogicManager users. Provide users_json as a JSON array or an object with a users array.”

Creates one or several LogicManager users in a single step, from a list passed in the Users JSON box.

When to use it
people added in another system need a LogicManager account, set up the same way each time.
Watch out
that box expects a list of users, or an object holding one, not one plain value per field.
7

Download Event Document

Action

In Zapier“Download one document from an event by document ID.”

Fetches one file stored on an event, by its document ID, so a later step can store or send it.

When to use it
evidence attached in LogicManager should be archived in your document storage too.
Watch out
three numeric IDs are required: event type, event and document. Get Event Documents can give you the last one.
8

Download Taxonomy Document

Action

In Zapier“Download one document from a taxonomy element by document ID.”

Pulls one document from a taxonomy element. The document list appears once type and element are chosen.

When to use it
a vendor certificate kept in LogicManager has to be shared with a team that has no access to it.
Watch out
set the type and the Element ID first, or the document picker stays empty.
9

Update Event

Action

In Zapier“Update one existing event. Choose event_type first, then select the event to update.”

Changes one event that already exists. You pick its event type, then point to the event by its ID.

When to use it
a status changes in another tool and the matching LogicManager event should follow.
Watch out
paired with New or Updated Event on the same type, this action can make the Zap loop.
10

Update Taxonomy Element by ID

Action

In Zapier“Update one taxonomy element. Choose taxonomy_type first, then select the taxonomy element to update.”

Edits one taxonomy element, picked by its type and its numeric ID, without creating a duplicate.

When to use it
a risk rating or an owner changes elsewhere and the register must reflect it.
Watch out
the ID must already be known; nothing here looks the element up by name.
11

Update Users

Action

In Zapier“Update one or more LogicManager users. Provide users_json as a JSON array or an object with a users array.”

Edits one or more existing users from a list in the Users JSON box. LogicManager matches each one by userNumber, loginId or email.

When to use it
a change recorded in another system should reach the matching LogicManager accounts.
Watch out
a user that matches none of those three keys is not updated.
Searches

LogicManager searches in Zapier

18 search steps look for data that already exists in LogicManager, so a later step can use it.

A search step looks something up in LogicManager and passes the result to the next steps. In the editor, the 18 LogicManager searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when a lookup goes sideways.

1

Get All Events by Type

Search

In Zapier“List events for an event type. For MCP use, prefer a filter and a small limit because unfiltered full scans can time out on large event types.”

Lists the events of one event type, for when a step needs several of them rather than one.

When to use it
a digest of every incident of a given type, built from one search.
Watch out
on a large type, a full unfiltered list can time out; narrow it with a filter and a small limit.
2

Get All Taxonomy Elements by Type

Search

In Zapier“List taxonomy elements for a taxonomy type. For MCP use, prefer filters, fields_to_include, and a small limit because unfiltered full scans can time out on large taxonomies.”

Returns the elements of one taxonomy type, so a later step can work through the whole family.

When to use it
copying your vendor list into another system in one pass.
Watch out
big taxonomies can time out when nothing narrows the list; restrict the fields and the number of results.
3

Get Control Monitoring Activities

Search

In Zapier“List monitoring activities for a control. For MCP use, prefer monitor_id for a single activity or limit for a short list.”

Lists the monitoring activities tied to one control of a plan.

When to use it
before logging a test result, find which activity of that control should receive it.
Watch out
both Plan ID and Control ID are required and numeric.
4

Get Event by Id

Search

In Zapier“Retrieve one event by event type and event ID, including all tabs and field values.”

Fetches a single event with all its tabs and field values, from its type and its ID.

When to use it
a later step needs the full details of the incident that just changed.
Watch out
use it rather than a list search when one event is enough; it is lighter.
5

Get Event Documents

Search

In Zapier“List documents attached to an event. Prefer document_name_filter when you only need a subset.”

Lists the files attached to one event, with an optional name filter when you only need some of them.

When to use it
find the document ID before Download Event Document fetches it.
Watch out
the event type ID and the event ID are both required.
6

Get Event Type by Id

Search

In Zapier“Retrieve one event type by ID, including profile fields and default workflows.”

Reads the definition of one event type, including its profile fields and default workflows.

When to use it
check which fields a type expects before a Zap creates events in it.
Watch out
it returns the type, never the events filed under it.
7

Get Groups

Search

In Zapier“List LogicManager groups. For MCP use, prefer group_name and limit instead of scanning every group.”

Lists the groups defined in LogicManager, filterable by group name.

When to use it
look up a group before Create Users places a new account in it.
Watch out
filter by group name and keep the limit small rather than scanning every group.
8

Get Monitoring Activities

Search

In Zapier“List monitoring activities for a plan. For MCP use, prefer a small limit or use Get Monitoring Activity by Id for one activity.”

Lists every monitoring activity of one plan, whatever the control behind it.

When to use it
build an overview of all the testing planned under a plan.
Watch out
for one activity only, Get Monitoring Activity by Id does the job with less noise.
9

Get Monitoring Activity by Id

Search

In Zapier“Retrieve one monitoring activity design by plan ID and monitoring activity ID.”

Retrieves the design of one monitoring activity, from the plan that owns it and its own ID.

When to use it
a test reminder should quote what the activity is meant to check.
Watch out
both IDs are numeric and required.
10

Get Monitoring Activity Metrics

Search

In Zapier“List metric results for a monitoring activity. For MCP use, prefer result_id for one metric result or limit for a short list.”

Lists the metric results recorded on one monitoring activity of a plan.

When to use it
send the latest results of a control test to the person who reports on it.
Watch out
use a result ID or a limit, or the list gets long.
11

Get Plan by Id

Search

In Zapier“Retrieve one plan by plan ID.”

Returns a single plan from its numeric ID.

When to use it
a message about a control should name the plan it belongs to rather than show a bare number.
Watch out
Plan ID is required; Get Plans helps you find it.
12

Get Plans

Search

In Zapier“List plans the user has access to. For MCP use, prefer a small limit and optional date filters.”

Lists the plans the connected user can access, with optional date filters.

When to use it
find a plan ID once, then reuse it in the steps that need one.
Watch out
it only shows what the connected account is allowed to see.
13

Get Plan Controls

Search

In Zapier“List controls for a plan. For MCP use, prefer control_id for a single control or limit for a short list.”

Lists the controls of one plan, or a single control if you pass its ID.

When to use it
fetch the control ID that Get Control Monitoring Activities requires.
Watch out
Plan ID is mandatory; keep the limit short on a large plan.
14

Get Plan Indicators

Search

In Zapier“List non-inactive indicators on a plan. For MCP use, prefer a small limit.”

Lists the indicators of a plan, leaving out the inactive ones.

When to use it
share the live indicators of a plan with a team outside LogicManager.
Watch out
inactive indicators never come back, so do not use it to audit retired ones.
15

Get Taxonomy Element Documents

Search

In Zapier“List documents attached to a taxonomy element. Prefer document_name_filter when you only need a subset.”

Shows every file attached to one taxonomy element, with an optional name filter.

When to use it
check whether a vendor already has a certificate on file before asking for a new one.
Watch out
Taxonomy Type and Element Id are both required.
16

Get Taxonomy Type

Search

In Zapier“Retrieve one taxonomy type definition, including its profile tabs and fields.”

Describes one taxonomy type: its profile tabs and the fields under them.

When to use it
see which fields a type holds before mapping Create Taxonomy Element.
Watch out
it describes the type only, never the elements filed under it.
17

Get Users

Search

In Zapier“List LogicManager users. For MCP use, prefer email or group filters and use limit when broad scans are acceptable.”

Lists LogicManager users, filterable by email or by group.

When to use it
check that someone already has an account before Create Users runs.
Watch out
without a filter the scan covers every user; set a limit if that is really what you want.
18

Get Taxonomy Element by Id

Search

In Zapier“Retrieve one taxonomy element by type and ID, including profile tabs and field values.”

Fetches one taxonomy element with its profile tabs and field values, from its type and its ID.

When to use it
a message about a vendor should carry its full record, not only its number.
Watch out
Taxonomy Type and the numeric Element Id are both required.

The three settings every search exposes

  1. Successful if no search results are found?
    On its default, a search that finds nothing stops the Zap and skips the steps that needed it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. LogicManager offers no such variant, so none of its searches shows it.
  3. If multiple search results are found?
    When several items match, you keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a LogicManager Zap breaks

Zapier attaches no help article to LogicManager, so the traps below are the general ones of Zapier, read through this app.

On a polling trigger Zapier remembers what it has already seen, so the same event does not start the Zap twice. The four cases below are the ones to plan for. If a Zap still misbehaves, see our Zapier troubleshooting page.

  • Past incidents are not picked up

    A Zap only reacts to what happens after you publish it. Events and elements that already existed stay out; moving that backlog is a separate job.

  • A Zap that sets itself off

    New or Updated Event followed by Update Event on the same type edits what the trigger watches, so the Zap restarts again and again and eats your tasks.

  • A bulk import held back

    After a migration or a mass import, a sudden batch of new elements can trip Zapier's flood protection, which holds the batch back instead of running it.

  • A search finds nothing

    A wrong Event Id or Plan ID returns nothing. On default settings the Zap stops at that search and the steps after it never run.
Need help

Need help automating LogicManager with Zapier?

A person reads every message.

FAQ

LogicManager Zapier integration: frequent questions

01Is the LogicManager Zapier integration free?
On the Zapier side, yes. LogicManager is not a premium app, so it works on the free plan, which gives 100 tasks a month and an unlimited number of Zaps. What the free plan restricts is the size of each Zap: one trigger and one action, nothing more. Catch Webhook followed by Create Event fits. Add Get Event Type by Id in between, or a filter, and the Zap becomes multi-step, which needs a paid plan. Your LogicManager subscription is a separate matter that Zapier does not handle.
02How many Zapier tasks does a LogicManager Zap use?
One per action that succeeds, none for the trigger. A Zap where New or Updated Event feeds one spreadsheet row uses one task per event that comes through. Put Get Event by Id in front to read every tab, and each event now costs two. The checks Zapier runs to find new events cost nothing, however often they happen. A step that fails is not billed. With 18 searches available, it is easy to stack steps, so count them before you size your plan.
03Does LogicManager trigger Zaps in real time?
One trigger does. Catch Webhook is instant: the request reaches Zapier and the Zap starts at once, on any plan, and the editor marks such Zaps with a lightning bolt. New or Updated Event and New or Updated Taxonomy Element are polling triggers. Zapier checks them on a timer that depends on the plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can also run a check by hand from the editor.
04What do you need to connect LogicManager to Zapier?
A LogicManager account, plus read or write access on every event type, taxonomy and plan you want a Zap to use but do not own. In Zapier, open the Apps page, click + Add connection, search for LogicManager, click Add connection, sign in in the tab that opens and grant access. The connection is made once and reused by every LogicManager step. Create Event and Create Taxonomy Element show their profile fields only once a type is chosen, so the account needs access to that type.
05Where do the numeric IDs of LogicManager steps come from?
Mostly from another LogicManager step. Event Type, Plan ID, Event Id and Element Id are required on many operations, and they expect numbers rather than names. The triggers hand over the ID of the event or element that changed. For the rest, a search does the work: Get Plans gives a plan ID, Get Plan Controls a control ID, Get Event Documents a document ID. Test the chain once with a real item before publishing, because a wrong ID makes a search come back empty.
06What if the LogicManager operation you need is not in Zapier?
Then the editor will not offer it: the catalog holds 32 visible operations, 3 triggers, 11 actions and 18 searches, nothing more. A chain of existing steps often covers the gap, for example Get Event by Id followed by Update Event to change an event found from its ID. What no chain gives you is a delete, of any kind, or a trigger on older changes than the last 24 hours. Those jobs stay manual in LogicManager, or move to another automation tool.
07Zapier, Make or n8n for LogicManager?
Decide on criteria rather than on a ranking. Coverage first: Zapier offers 3 triggers, 11 actions and 18 searches for LogicManager, so check that any other tool exposes the operations your process relies on. Billing next: Zapier counts one task per successful action, which stays readable when the volume of events is steady. Then reaction time: only Catch Webhook is instant here. Hack'celeration has no LogicManager page for Make or n8n, so this page only covers Zapier.
Same platform

Other docs you might need on this stack.

Browse all integrations