Which marketing systems can we use?

Use the current capability catalogue and provider-specific guides to check the supported actions and resource boundaries. Google Ads, Meta, analytics, CRM and file workflows each need approved configuration; a platform name is not a promise of every integration or action.

Does Outloop optimize campaigns automatically?

Outloop provides the client Workspace and approved working access for supported AI tools. A specific optimization workflow needs its own setup, decisions and verification. The published campaign-build demo makes no ad-performance or autonomous-optimization claim.

Can we reuse what works for another client?

A reviewed, client-neutral method can be reused deliberately. Client results, private Context, files and account identities stay with that client; learning is not automatically shared across Workspaces.

What needs human approval?

Your workflow must identify the decisions and actions requiring review, such as campaign messaging, spend or publication. Access to a system does not by itself mean every business action is approved.

Is the campaign demonstration a customer performance case study?

No. It uses a demo brief and assumptions with actual Google Ads and Meta campaign objects kept PAUSED. Review emails are labeled staged reconstructions. It does not prove ad delivery, spend or performance.

For AI marketing agencies running AI workers across client accounts

Run more client marketing work with clear client boundaries.

Serve more clients — without rebuilding access for every client account.

Take me out of the damn API loop.

Operate AI across client marketing accounts, files and review steps. Separate Workspaces, recorded campaign-build evidence and a practical path to your first workflow.

Reuse the method. Configure each client. Keep private state separate.

Start 14-day trial Download for Mac

Create your trial. Download the Mac app. Run your first API proof locally.

Setup guides + product support included · API keys stay local · Cancel anytime

outloop marketing access vault stays locked

Outloop client workspace and approved access

One access setup Workspace approved Runtime allowed secret_exposed:false

Watch a marketing brief reach the ad accounts.

Follow the approved assets, commercial review and campaign execution behind one client launch.

Approved client Context and brand assets
Human review before execution
Real campaign objects, kept PAUSED

Start 14-day trial Download for Mac

Create your trial, then install on your company-controlled Mac. Set up your first workspace.

67-second Ellātu preview · Google Ads + Meta · No form required

Demo brief and assumptions. Real Google Ads and Meta execution, configured PAUSED. Review emails are labeled staged reconstructions. No delivery or performance claim.

Open video directly Read the English transcript Explore the complete 8:53 workflow →

Reuse approved API access across the runtimes your team already uses

One approved access layer for Cowork-style sandboxes, Claude Code, Codex, Hermes, and OpenClaw — without rebuilding setup for every platform. Add or change an approved runtime; context and approved access stay attached to the client workspace.

One credential. The right workspace. Any approved agent runtime. secret_exposed:false

Independent tools. Names and logos belong to their respective owners; Outloop is not affiliated with or endorsed by these projects.

Client-bound work across supported tools

01

Client task

Start with the intended client and a defined result.
02

Approved Workspace

Use this client’s Context, accounts and resources.
03

Supported action

Work through the approved API, browser or file path.
04

Reviewable result

Inspect the output and involve a person where required.
05

Work history

Keep the work record with the intended Workspace.

Conceptual workflow. Supported actions depend on the configured service, runtime and approved resources.

Use case · AI marketing agencies

Outloop for AI marketing agencies

Last updated: October 3, 2026

In short

Outloop is Workspace infrastructure for deploying and operating AI workers.

Outloop helps agencies operate AI work in separate client Workspaces, with approved context, accounts and resources. The recorded campaign workflow connects a client brief, creative work and human review to real Google Ads and Meta builds, kept PAUSED.

Open in: ChatGPT Claude Perplexity

Client AWorkspace

Context: Client A’s brief & rules
Accounts: Google Ads A · Meta A
Resources: CRM A · Drive A
Browser: Approved identity A
Access: Approved for Client A

Work stays with this client.

Client BWorkspace

Context: Client B’s brief & rules
Accounts: Google Ads B · Meta B
Resources: CRM B · Drive B
Browser: Approved identity B
Access: Approved for Client B

Work stays with this client.

Illustrative client setup. Each service and resource needs its own approved access; Local Chrome uses the Workspace’s configured profile; Managed Browser uses a shared profile with approved identity and access. Diagram, not recorded execution.

The work crosses platforms. The client should stay clear.

Performance teams connect ad accounts, analytics, tagging, CRM outcomes, creative files and reporting. The hard operating question is whether every step belongs to the same client, uses the approved resources and reaches a result a person can review.

Outloop organizes supported AI work around separate client Workspaces. The opportunity is broader than optimizing inside one advertising platform: it is managing the cross-system job with the right client context and access.

For the general category, start with what marketing AI agents do. This page helps an agency evaluate its operating setup.

A campaign build you can inspect

The Ellātu demonstration follows a brief and approved assets through creative work, human judgment and actual Google Ads and Meta campaign builds. The campaigns remain PAUSED.

The commercial assumptions are demo inputs. Review emails are staged reconstructions, clearly labeled. This shows a bounded production task; it does not show customer ROI, live delivery or an independently measured efficiency gain.

Watch the complete workflow and its evidence.

Agency workflow proof

Built from real agency API workflows.

Outloop was built while running real client-agent workflows across ads, CRM, data, file, reporting, and automation APIs.

The lesson was simple: agencies don't need another place to paste keys. They need one approved access layer that lets agents work across client workspaces safely.

Explore agency API workflows

Google Ads Campaign checks

Meta Ads Account reporting

Merchant Center Product feed review

Airtable CRM & ops data

Google Drive Client asset folders

Gmail Inbox workflows

Apify Data collection

Firecrawl Web research

Example services shown for workflow context. Logos and names are trademarks of their respective owners; no official integration or endorsement is implied.

Map the next workflow before automating it.

Workflow planning opportunities—not a claim that every combination is prebuilt
Job	Systems to confirm	Reviewable result
Client reporting	Approved ad accounts, GA4 property, CRM data and destination Drive	A report with sources, time range and client identity checked
Creative production	Approved assets, supported creative tools and client file destinations	Assets reviewed before publication
Attribution review	Approved analytics, GTM and CRM access for the intended client	Findings and proposed changes; no silent tracking edits
Campaign preparation	Approved Google Ads or Meta accounts, brief and budget decisions	A checked draft or paused build before launch

Check the capability catalogue for each required operation. A useful workflow depends on supported actions, correct client resources and explicit review—not on displaying a row of platform logos.

Shared agency access needs a client boundary.

An agency manager login can reach several clients. The task must still stay with the approved account and resources for the current Workspace. These actual demo captures show both approved work and specific refusals.

How shared-login resource control works · Google Ads setup · Meta setup · Drive setup.

Connect the supported stack once. Configure each client Workspace.

For supported multi-client Google Ads or Meta setups, reuse the existing platform integration and reviewed workflow logic. Configure the next Workspace with that client’s approved ad account and resources, Context, assets and review requirements, then validate the target and output.

The recorded allowed/refused requests demonstrate specific configured resource boundaries. They are not a timed second-client onboarding demonstration. Implementation reuse is qualitatively proven; no “few clicks,” automatic environment clone or measured onboarding gain is claimed.

How implementers reuse the foundation · Configure a recurring client report.

Start small, then repeat what is verified.

Choose one client and one deliverable. Add approved Context, configure the necessary access, verify the account boundary and inspect the result. Expand only after the workflow works as intended.

Outloop runs on a company-controlled Mac today. Bring your supported AI tools and provider accounts; implementation help is scoped separately. Set up your first Workspace or scope implementation effort.

How it works

How you reuse API access in 3 steps

Add it once. Approve the workspace. Let the agent use it safely.

Outloop “Add an API key” panel: a “No terminal needed” badge, a service picker set to Google Ads, and a Workspace-dedicated access selector.

Add API access once

Choose a service, select the workspaces that should get access, and store the credential locally on the Mac.

Keys stay local

Outloop workspace approval: the outloop-website workspace selected to receive access, with a suggested key name and an empty “Paste the API key” field.

Approve the right workspace

Grant access only to the client workspace that should use it. Each workspace stays isolated.

Wrong-client access blocked

Outloop agent-projects panel: the Claude / Cowork runtime expanded to show per-project status (Needs action, Ready, Need to connect), above the Claude Code, OpenClaw, and Hermes Agent runtimes, with an “Agent keeps working — secret_exposed:false” proof badge.

Let agents use approved access

Connect agent projects, then let approved agents request access through Outloop without seeing the raw key.

Agent keeps working secret_exposed:false

Keys stay local Workspaces stay scoped Agents request access, not keys

Scoping this for a client? Estimate the implementation — hours, timeline, dependencies and a printable proposal, with your own rates.

Marketing APIs your agents already touch

The same approved-access pattern applies to every marketing API an agent uses. A few examples:

Why we think marketing work is heading this way is set out in the AI Agency Manifesto.

✓Google Ads — one agency manager (MCC) login, each workspace pinned to its own client customer ID; a request naming an unapproved customer ID is refused. AI agents for Google Ads → · How to connect the Google Ads API → · how resource pinning works →
✓Meta Ads — account reporting and campaign actions without the system-user token ever reaching the agent. How to connect the Meta Ads API →
✓Merchant Center, GA4 & Search Console — product-feed checks, analytics pulls, and search performance, each scoped to the right client property.
✓CRM & data tools — check supported operations and configure each client’s approved resources.

Client context, and learning that a human approves

Access is half the problem. The other half is that an agent starting a task for a client usually starts blank — it does not know the brand rules, which logo is the approved one, or what the client has already said not to claim. So the operator re-explains it, every run.

Each client workspace holds its own approved Context: brand and tone guidance, approved references and assets, communication rules, and constraints on what may be claimed. The agent retrieves it before it generates anything. Context is knowledge only — it never grants API permission, and it stays scoped to that one client.

Client workspace Context — retrieved before work, versioned, restorable. proven in product
Learning receipts with human review — approve, edit, reject, or defer. proven in product
An approved lesson improving a later run — seen end to end in a real agency creative workflow. verified in a real workflow
A lesson updating a Skill — tracked separately from the Context loop. operator-confirmed

Nothing updates itself. The agent proposes a lesson; a person approves it; only then does it become a new Context revision — and revisions can be rolled back. There is no model training, no self-rewriting, and no learning that crosses from one client to another.

Service names are examples for workflow context and are trademarks of their respective owners; no official integration or endorsement is implied. Outloop is the runtime access layer the agent uses — you bring the approved API access.

Keep your vault. Control runtime access.

macOS Keychain Supported today

1Password Not yet supported

Infisical Not yet supported

Doppler Not yet supported

Today Outloop keeps approved credentials in macOS Keychain on your company-controlled Mac. Direct integrations with external vaults such as 1Password, Infisical and Doppler are not supported yet. Outloop never replaces your vault — it controls which workspace and runtime can use approved access.

No API keys uploaded to cloud.
No raw key returned to the agent.
No .env files required.
Wrong-client access is blocked before credential use.

Real ad-platform execution — and the refusals that protect other clients

A demo workspace running Google Ads and Meta Ads work through Outloop. The approved accounts execute; a request aimed at another account or at a campaign outside the bound ad account is refused.

Outloop Live Activity for demo workspace 018: Google Ads and Meta Ads requests, each marked Allow with result OK, including grouped batches of 10 and 14 requests. — Allowed: approved API work executes

Demo Workspace 018 · Google Ads and Meta Ads requests
Every row: **Allow · OK** — including grouped batches of 10 and 14 requests
The approved requests returned results in this client Workspace

Outloop Live Activity for demo workspace 018: allowed google_ads and meta_ads requests interleaved with three refused requests — two marked Deny with RESOURCE_ID_NOT_ALLOWED (one google_ads, one meta_ads) and one meta_ads request marked Deny with META_OBJECT_NOT_APPROVED. — Refused: these wrong-resource requests did not run

**Deny · `RESOURCE_ID_NOT_ALLOWED`** (google_ads and meta_ads) — the request named an account outside this Workspace’s approved resources; the requested action was refused
**Deny · `META_OBJECT_NOT_APPROVED`** (meta_ads) — a campaign, ad set or ad that does not belong to the approved ad account; the requested action is not sent to Meta
Approved requests in the same workspace keep executing around the refusals — **Allow · OK**

Real execution in an Outloop demo workspace (workspace 018), published in the September 26, 2026 proof pack — not a customer case study, and not evidence of ad spend, delivery or performance. Enforcement covers requests routed through Outloop. See the runtime access walkthrough for the recorded flow.

What Outloop enforces — and where the boundary is

What Outloop enforces

Approved requests are scoped to the configured client accounts and resources.
Recorded Google Ads and Meta examples show both allowed and refused requests.

What it does not guarantee

Controls apply to supported work through Outloop and depend on correct configuration.
Business decisions and publication still need your review rules.

What you still configure

Configure each client Workspace with its own Context, accounts, resources and review requirements.
Validate the workflow and result before expanding.

Is this for you?

A good fit if…

You run paid media, content or reporting for several clients with AI agents.
Client ad accounts, analytics and files must stay separate.
Work needs approved assets and human sign-off before anything goes live.

You may not need Outloop if…

You only use AI for copy drafts and never give it access to client accounts.
You serve one client, or every client already has fully separate credentials, machines and agents.
You need a hosted, cloud-only service with no company-controlled Mac.
You need a compliance certification on file before you start.

Run more client marketing workflows — safely.

Outloop is available with setup guides and product support for AI marketing agencies, operators, and dev shops.

The local-first app is signed with a Developer ID and notarized by Apple, and two-Mac reproduction was first verified with release v1.1.6 on 24 July 2026 (a historical milestone, not a statement about the current release). See the security model, the broader AI agencies use case, a real anonymized workflow, or pricing.

Start 14-day trial

See the client work behind the workflow.

A website rebuild. A missing conversion step. A team directing the work. Adam walks through one real client project with an AI worker and Outloop.

Watch the founder case study