How does OCNORA authenticate with Google Pollen?

With a stored API key credential, shaped the API key as raw text. A connection test can check it when you add it.

What can I automate with Google Pollen?

2 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Google Pollen operation I need is not listed?

Where Google Pollen has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use Google Pollen?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google Pollen calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

Google Pollen

Business appsAPI keyConnection test available

The Pollen API (Google API key).

OCNORA ships 2 typed Google Pollen operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about Google Pollen Google Pollen API docs ↗

Before you connect Google Pollen

Authentication: API key
Credential: the API key as raw text
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with Google Pollen

Operations, grouped by what they do to your data.

Read and search 1

Lookup Heatmap Tile

Other operations 1

Forecast

A sample Google Pollen workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Pollen trigger is needed.
2
Lookup Heatmap Tilepollen.lookup_heatmap_tile
Returns a byte array containing the data of the tile PNG image.
3
Forecastpollen.forecast
Returns up to 5 days of daily pollen information in more than 65 countries, up to 1km resolution.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Operations 2

Google Pollen questions

How does OCNORA authenticate with Google Pollen?: With a stored API key credential, shaped the API key as raw text. A connection test can check it when you add it.
What can I automate with Google Pollen?: 2 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Google Pollen operation I need is not listed?: Where Google Pollen has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Google Pollen?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Google Pollen calls controlled?: Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Google Pollen workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.

Book a technical demo Talk to sales