Power Automate

If your organisation already runs on Microsoft 365, Power Automate is the path of least resistance: the flow that validates an address can be the same flow that writes it to a SharePoint list, posts to Teams and updates Dynamics, with no hop out to a third-party platform and no data leaving your tenant on the way.

Two connectors, not one

Which connector you install depends on what you are automating. They are separate listings with separate catalogs.

VerveCRM — data quality on customer records. Email deliverability and disposable-address checks, phone validation, street-address parsing, postal-code and IP lookup, currency conversion, sales tax, company and sanctions screening. About thirty endpoints, chosen for the moment a contact or account record is created or updated.

VerveKit — general-purpose capability for makers building agents and apps: weather, exchange rates, DNS and domain lookups, sentiment, translation, holidays and the rest of the VerveKit catalog.

Both authenticate the same way and both bill the same way. Install whichever matches the work; installing both is fine and they will not collide.

Named actions and the dynamic action

Each connector gives you two ways to call an endpoint, and the difference is discoverability rather than capability.

Named actions are the common operations spelled out — Validate an email address, Calculate sales tax, Get a weather forecast. They appear directly in Power Automate's action search, with their own inputs and outputs, so a maker who types "validate email" finds one without knowing APIVerve exists. Use these when one fits.

The dynamic action covers everything else in that connector's catalog. Pick the endpoint from a dropdown and the inputs redraw to match. It sits under the advanced settings because it is the general case, not the common one.

The dropdown is scoped to the connector you are using — VerveCRM lists its thirty, VerveKit lists the VerveKit catalog. That is deliberate: two connectors that could both call everything would be the same connector twice.

Connecting

The first time you add an APIVerve action, Power Automate prompts you to create a connection. Sign in and authorise it; the connection is stored in the environment and appears under Data → Connections, where it can be shared with other makers or revoked.

The connection stores an API key and sends it on every action. There is no separate account-linking step of the kind Zapier and Make run, so a sub-key is accepted here — and is usually the right choice, because a connection in a shared environment can be handed to other makers who never see the value but can spend against it. Scope the sub-key to the endpoints your flows use.

Rotating the key breaks the connection for every flow in the environment at once, so treat rotation as a change that needs a window rather than something to do casually on a Friday.

Building a flow

Trigger. Anything Power Automate offers — a new Outlook mail, a SharePoint item created, a Teams message, a recurrence, or an HTTP request for a webhook.

The APIVerve action. Add it, pick the operation, and fill the inputs from dynamic content produced by the trigger.

Everything after. The action's outputs are available as dynamic content in later steps, so you can branch on the result with a Condition, write it to a list, or compose it into a message.

The pattern that earns its keep is putting a Condition immediately after the action and treating a failure as a route rather than an exception — a flow that stops dead at 2am because one address was malformed is worse than one that files it for review.

What it costs

One call per action execution, at that endpoint's rate, identical to calling the API directly. Choosing an endpoint in the dropdown and loading its inputs cost nothing.

Power Automate's own licensing is counted separately and does not line up with ours. Two things to watch on the APIVerve side:

Apply to each. A loop over a SharePoint list calls the endpoint once per item. A 2,000-row list is 2,000 calls, and Power Automate's default concurrency will fire them fast enough to meet the rate limit. Set the loop's concurrency control down rather than leaving it at the default when the list is large.

Recurrence. A five-minute trigger is roughly 8,640 runs a month before it does anything useful. Turn on the usage alert in settings.

Building your own connector

If neither published connector fits — you want the full catalog, or a different curated set for an internal audience — the connector definition is an OpenAPI document you can import as a Power Platform custom connector. The OpenAPI specs for every endpoint are published, and a custom connector built from one behaves like any other action in your environment.

This is also the answer for the file-upload endpoints, and for anyone whose governance policy requires the connector to live in their own tenant rather than come from a publisher.

When it fails

401 — the connection, not the flow. The key stored on it was rotated or revoked; a sub-key is accepted here, so that is not the cause. Recreate the connection under Data → Connections.

400 — an input is wrong and the message names it. Most often dynamic content that resolved to empty on that run. The run history shows the exact inputs and outputs of every action, which is the fastest way to see what was actually sent.

429 — the rate limit, or the account is out of calls. Nearly always an Apply to each running at full concurrency. Check the balance in analytics; if there is balance, lower the loop concurrency.

The action times out. Connector calls are cut off at 25 seconds. Rendering endpoints — screenshots, PDFs — can exceed that on a heavy page; use the HTTP action with your own timeout for those.

The connector is not in the search. It has not been installed in that environment, or you are in a different environment from the one it was installed into. Environment is the usual culprit.

Next

Making requests covers the direct call a custom connector or HTTP action would make, and all endpoints is the full catalog. n8n is the closest equivalent outside the Microsoft estate, and integrations compares every platform side by side.