Integrations

How Avago integrations work — three tiers

Native, automation, API. Which to pick for a given tool, and how each one is set up.

Article11 min·Updated 10 June 2026·By Avago team

The three tiers

Avago connects to other tools through three tiers, and picking the right one is mostly about how deep the connection needs to be:

  • Native — ready-made marketplace integrations for popular tools.
  • Automation — a flow builder for chaining actions across apps.
  • API + webhooks — an open, programmable layer for anything bespoke.

Start at the top: if a native integration exists for your tool, use it. Drop to automation when you need to connect steps, and to the API only when nothing above fits.

Native — the marketplace integrations

Native integrations are the quickest path. These are pre-built connections to tools like Mailchimp, Slack, HubSpot and Google Business. You connect them from the Integrations area, usually through a one-time OAuth sign-in, then choose a few options — which audience, which channel, which fields. No code, no maintenance. For the common jobs — newsletter signups, form alerts, contacts into a CRM — a native integration is all you need.

Automation — the bundled flow builder

When you need if this, then that logic across tools, the automation flow builder handles it. You build a flow from a trigger and one or more actions — for example, "when a form is submitted, add the contact to Mailchimp and post to Slack and create a task." It's visual, so you assemble flows without writing code, and it covers the cases a single native integration can't express on its own.

API + webhooks — for everything else

For anything custom, Avago exposes an open API and webhooks:

  • Webhooks push events out of Avago to your own systems in real time — a new form submission, an order, a publish.
  • The API lets your code read and write data programmatically.
  • Access uses per-scope tokens, so each integration only gets the permissions it needs, and every token's activity is recorded in an audit log.

Choose the lowest tier that does the job. Native is the least to maintain; the API is the most powerful. Most small businesses never need to go past native and a little automation.

Was this article helpful?

Your vote tunes the rank order for everyone else. We read every “no” comment.

Need account-specific help?Atlas has read every article on this site and can answer in your account context.
Ask Atlas →

Read next. From the same section.

All in Integrations

Have an idea? Just have a go.

Your website is waiting to be built. No credit card. No commitment. Free to build — only pay when you're ready to go live.

Free to build~5 min to liveNo credit card