Integrations

Prometiam node for n8n

Put company data in a workflow: search a company by name or register number, resolve up to 100 in one call, check insolvency notices, validate a VAT number or an LEI, and screen a name against sanctions lists (beta).

• npm n8n-nodes-prometiam
• Licence MIT
• Status Verified on n8n Cloud

Install

1. On n8n Cloud, search for Prometiam in the nodes panel and add it. On a self-hosted instance, open Settings, then Community nodes, then Install, and enter n8n-nodes-prometiam.
2. Add a Prometiam API credential and paste your key (it starts with rk_live_). Saving it makes one free call to check the key.
3. Pick a resource and an operation. Each operation returns one item per result.

n8n-nodes-prometiam

The node needs a key. To try the API before you have one, use the public demo key from the docs.

Operations

A batch lookup counts every item. Sanctions screening is part of the Professional plan; a trial key has 25 screens a month.

Workflow: check a supplier

Three nodes: find a company by country and register number, validate its VAT number, then search insolvency notices. Import the file, choose your credential, change the country and number.

1. Find the companyCredits: 1
2. Validate the VAT numberCredits: 1
3. Search insolvency noticesCredits: 2

One run costs 4 credits.

The VAT step needs a company that has a VAT number, and VIES covers EU countries only, so the example uses Spain. Insolvency notices exist for sixteen markets, corporate only.

The credential

Create a key (the 14-day free trial gives one), add a Prometiam API credential in n8n and paste the key into the API Key field. The node sends it as Authorization: Bearer <key> to https://api.prometiam.com/functions/v1/risk-api. That address is fixed in the node, so a workflow cannot send your key to another host. Saving the credential tests it with one call to GET /account, which costs no credits.

One operation and its output

Add the Prometiam node, choose Company, then Search, and set Country to Spain and Name to Inditex. Every result becomes one n8n item, shaped like the API’s company object (trimmed here):

[
  {
    "id": 1741526,
    "match_score": 100,
    "country": "ES",
    "company_number": "A15075062",
    "company_name": "INDUSTRIA DE DISEÑO TEXTIL, S.A",
    "legal_form": "SA",
    "status": "active",
    "founding_date": "1985-06-12",
    "city": "ARTEIXO",
    "vat_number": "ESA15075062",
    "vat_number_source": "rule"
  }
]

vat_number_source is rule: the VAT number is built from the register identifier, its format is right, but the registration is not confirmed. That is why the workflow above validates it in its next node. For the full profile, add Company, then Get and pass the id with the expression {{ $json.id }}; under Options, Include attaches the risk flags, the insolvency notices, the LEI record or the procurement awards.

Credits, rate limits and batching in a workflow

• Every input item makes its own API call, and all of them are sent at once. A hundred items into Company, then Get is a hundred calls and a hundred credits.
• Per-minute limits by plan: free trial 10 requests, Starter 60, Professional 120, Scale 300. Over the limit the API answers 429 with a Retry-After header. Under Options, add Batching (Items per Batch and Batch Interval in milliseconds) to space the requests out; the defaults send 10 items every 60 seconds, which fits the free trial.
• To resolve a long list, use Company, then Look Up (Batch): up to 100 companies in one call, one credit per item, and a status of found, not_found, error or timeout on each row. An over-quota batch is refused up front with 429 batch_exceeds_quota and max_items_now. Batch sanctions screening needs a paid plan: the free trial screens one name at a time. The Idempotency Key option replays the same batch safely for 24 hours without using credits again.
• Errors are free. A rejected key or a 429 stops the node with the API’s message; switch on Continue On Fail to handle it in the workflow.
• A search with no match returns no items and the branch stops. Switch on Always Output Data in the node’s settings to carry one empty item on.

Countries and the limits of the nine operations

Company operations take a country code; the docs name what each country’s register offers. The limits that matter in a workflow:

• Insolvency, then Search covers corporate notices only, in sixteen markets: FR, DE, GB, AT, CH, NO, FI, US, NL, DK, HR, SE, ES, LV, EE and SG. Give at least one filter. No notice found is not proof of solvency.
• Validation, then Validate VAT Number covers the EU member states plus Northern Ireland (XI); Greek numbers use the EL prefix and GB VAT numbers are out of scope. If a member state’s service is down, the operation fails with 503 (retryable) instead of reporting the number as invalid.
• Sanctions Screening, then Screen is beta: 3 credits per name, on the Professional plan (a trial key has 25 screens a month). PEP screening is beta and Spain only.
• Officers come with Company, then Get for Spain, France, the United Kingdom, Norway and Poland only (Polish natural persons are masked by the register). Every other country returns company records only.
• The node covers the nine operations in the table. Events, monitoring and financial statements are not among them: call those endpoints from an HTTP Request node with the same key, or from the SDKs.

When to use the node

• Supplier or customer onboarding: a form or a spreadsheet row triggers a search, a VAT validation and an insolvency search, and the result goes to Slack, a ticket or a CRM. The workflow above does this for one company.
• A scheduled check of a supplier list: a Schedule Trigger reads the list, Look Up (Batch) resolves it and Insolvency, then Search flags notices.
• Enriching CRM rows: a company number or name in; legal form, status, address and activity code out.
• Prefer the SDKs when the logic lives in your own service, the Postman collection to try requests by hand, and the MCP server when a person asks questions from an AI assistant.

Questions

Limits that apply everywhere

• Sanctions screening is beta. PEP screening is beta and Spain only.
• Insolvency notices are corporate only, in sixteen markets.
• Monitoring covers every live country except France and Chile.
• Officers are served for Spain, France, the United Kingdom, Norway and Poland (Polish natural persons are masked by the register). Every other country is company records only.

Contains CVR data (Erhvervsstyrelsen), CC BY 4.0.

More

• Integrations
• What's new
• View API Docs