# Integrations

How your Agent connects outside services to a Workflow, from understanding the task to checking a useful result.

Last updated: 2026-10-23

Typenode Workflows use the APIs of outside services to read data and carry out actions. Describe
what you want to achieve to your Agent; it can work out the requests, data and account access the
Workflow needs, then help you connect and check them.

## Start with the task

You can install a Template as a starting point or ask your Agent to build a Workflow for your own
task. A Template supplies an initial design and setup requirements; your Agent can adapt its
independent copy when you need something different.

Explain the result you want, which accounts or resources it concerns, and when it should happen.
Your Agent can research the service's API and identify the operations and inputs needed to get
there. You do not need to choose an endpoint or an authentication method before describing the
problem.

## What the Agent works out

The service's API defines what is possible and what access it requires. Your Agent can use its
official documentation, Typenode's Application catalog and the provider references here to assess
the task. That includes the relevant operations, account permissions, API availability, product
conditions and any quotas or costs that matter.

These sources give the Agent facts to reason from. They do not prescribe every request or limit
it to a fixed list of prebuilt actions. A service without its own reference Article may still be
usable; the Agent needs to establish whether its API and authentication requirements can be met,
rather than assume support from the service's name.

Where there is a meaningful choice, your Agent can explain the options and ask for your preference.
It can then configure the requests and the values your Workflow uses. If a different connection
method needs different headers or account settings, it can adapt the draft accordingly.

## Connect the required access

Some services use a copied API key; others ask you to authorize an account. Sensitive values and
account consent go through secure browser setup, not chat. Your Agent prepares the relevant setup
and continues after you complete it.

[Managed and custom OAuth apps](/integrations/managed-and-custom-oauth-apps) explains those two
registration routes. [Credentials](/configuration/credentials) and [Secrets](/configuration/secrets)
explain the account access and hidden values a Workflow uses.

A successful setup should lead to a useful request against the intended account or resource.
Authorization alone does not establish that every operation or property is accessible. The Agent
can check the actual result and use the service's response to work out what remains to configure.

## Use the provider references

Provider Articles record Typenode's current managed setup, exact supported OAuth scopes and
service-specific access conditions. They help you and your Agent decide whether a task fits the
available route or needs another setup.

The [Google reference](/integrations/providers/google) covers its enabled managed API and the relevant
custom-app requirements. For complete tasks and reusable external setup, use
[Tutorials](/tutorials).