- Home
- Resources
- Integrations
- OpenRegister
OpenRegister Zapier integrationAutomate OpenRegister with Zapier.
The OpenRegister Zapier integration gives you 0 triggers, 4 actions and 1 search to pull company data from official German sources into your other tools: details, financials, holdings and owners of a company, found by its name.
Verified Trustpilot reviews · AI, automation & growth agency
What the OpenRegister Zapier integration actually does
OpenRegister is where you look up a German company and read what the official registers say about it: who it is, its figures, who owns it. Through Zapier, that data flows into your CRM or sheets without code: a Zap (the automation you build on Zapier) starts on an event in another app, then asks OpenRegister about the company.
Three results justify the setup. Enriched company records: a new company in your CRM goes through Find Company by Name, then Get Company Details, and the official details land back on the record. A quick financial check: Get Company Financials hands a prospect's figures to your sales or credit team before a call. Who owns whom: Get Company Owners and Get Company Holdings map the owners of a company and the stakes it holds, useful for compliance checks or account mapping.
The limits are just as clear. OpenRegister has no trigger on Zapier: nothing in the register can start a Zap, so a change in a company's filing never reaches you on its own. All four actions read data and write nothing back to OpenRegister. Each one needs the company picked from a list or mapped as an ID, which in practice means a search step first, and that makes the Zap multi-step. And the data comes from German official sources, so the tool serves companies registered in Germany.
Before choosing, you can read Make vs Zapier and our Zapier review.
Zapier vocabulary in one minute
Eight words carry the whole page. Each is explained once here, then used as is.
- Zap
- The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event that starts the Zap. With OpenRegister, it always comes from another app, such as your CRM or a form.
- Action
- What the Zap does after it starts. Here, each OpenRegister action fetches one kind of company data for the next steps.
- Task
- The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by its app, with no wait for a check.
- Filter
- A step that lets the Zap continue only when the incoming item meets your condition, and stops it there otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
- Connection
- Your OpenRegister account linked to Zapier once, then reused by every step of every Zap that queries OpenRegister.
What an OpenRegister Zap really costs
Zapier bills tasks, not Zaps. The trigger of the source app never costs a task, and neither does Zapier checking it for new items. What you pay for is the OpenRegister actions.
- TriggerNever costs a task
- Action that succeeds1 task each
- Action that failsNot counted
- Free plan100 tasks a month, two-step Zaps only
Each action that succeeds counts once, even though it only reads: a Zap that gets a company's details and then its owners uses two tasks per company. An action that fails is not counted. OpenRegister is not reserved to paid plans, so it works on the free plan, with 100 tasks a month and unlimited Zaps. The catch: the free plan only builds two-step Zaps, one trigger and one action. Adding Find Company by Name, a second action or a filter makes it multi-step, and that needs a paid plan. The interval grid applies to the trigger of the source app when it works by polling.
Connect OpenRegister to Zapier in 3 steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. You need an OpenRegister account first, since every action and the search run through it.
- 02
Pick OpenRegister
Type OpenRegister in the search box of the dialog, select it, then click Add connection. Zapier opens a new tab so that you sign in directly on OpenRegister's side.
- 03
Sign in and grant access
Log in to OpenRegister in that tab and allow Zapier to use the account. The connection is then saved once and offered again in every step that queries OpenRegister.
Your first OpenRegister Zap
GoalEach new company in your CRM is matched in OpenRegister and enriched with its official details.
- 01
Build: choose the trigger
Create a Zap and pick your CRM with its new company event. OpenRegister cannot start a Zap, so the starting point always lives in another app.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent companies of your CRM, so you map the next steps on a real company rather than a blank.
- 03
Find the company
Add the OpenRegister search Find Company by Name and map the company name from the CRM. Decide what happens if nothing is found or several companies match.
- 04
Get the details
Add Get Company Details and map the company found by the search into its Company field. Then add the CRM action that writes those details back on the record.
- 05
Test and publish
Test each step once and read what came back from OpenRegister. When the record looks right, click Publish to switch on this multi-step Zap.
OpenRegister actions
OpenRegister gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Get Company Details
ActionIn Zapier“Retrieve detailed information about a company.”
Fetches the detailed information OpenRegister holds about one company and hands it to the following steps. It is the action that turns a bare company name into a complete record.
Get Company Financials
ActionIn Zapier“Retrieve financials for a company.”
Pulls the financials OpenRegister has for a company, so a later step can store them or pass them to a person who decides.
Get Company Holdings
ActionIn Zapier“Retrieve holdings for a company.”
Returns the holdings of a company, the other companies in which it has a stake, so the next steps can see how far a group reaches.
Get Company Owners
ActionIn Zapier“Retrieve owners for a company.”
Retrieves the owners of a company, for a later step to log or check. Paired with Get Company Holdings, it gives both directions of a group structure.
OpenRegister search
1 search step looks for data that already exists in OpenRegister, so a later step can use it.
A search step finds something that already exists and hands it to the next steps. In the editor, the OpenRegister search sits at the bottom of the Action event list, under SEARCH. Like any extra step, it makes the Zap multi-step. Three settings decide what happens when the result is not the one you expected.
Find Company by Name
SearchIn Zapier“Search companies by name.”
Looks up companies in OpenRegister from a name you type or map, and hands the company it finds to the next steps. It is the bridge between the name in your CRM and the ID the four actions expect.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that needed it. Turned on, the Zap carries on with an empty value.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Find Company by Name does not offer it, which makes sense: OpenRegister reads registers and creates nothing.
- If multiple search results are found?Several matches: keep the first one (the default), stop the Zap, or pass all of them on. With company names, this setting deserves a careful look.
When an OpenRegister Zap breaks
Zapier attaches no help article to OpenRegister and its listing documents no limit of its own. The breakdowns below come from how Zapier works, applied to company lookups.
Most trouble comes from the search step and from history nobody enriched. If a Zap misbehaves, our Zapier troubleshooting page is the next stop.
Existing accounts stay bare
A Zap only reacts to what happens after you publish it. Companies already in your CRM are not enriched: running them through OpenRegister is a separate job.No match stops the Zap
If Find Company by Name finds nothing and the setting is left on its default, the Zap stops there and the Get Company steps are skipped for that record.The wrong company kept
When several companies match a name, the search keeps the first one by default. A common name can enrich your record with another company's data.A bulk import held back
Import a large list of companies into your CRM at once and its trigger may return a huge batch. Zapier's flood protection can hold it back instead of running it.
Need help automating OpenRegister with Zapier?
A person reads every message.



