Custom Pipelines

Custom Pipelines let teams turn repeatable marketing operations into AI-built, production-ready workflows. Instead of manually running one-off scripts, stitching tools together, or asking engineering to build every custom automation, users can describe the workflow to Improvado Agent and get a reusable pipeline that can be run on demand or scheduled.

At a business level, this is useful when a process is too specific for a standard product feature, but too recurring or valuable to keep doing manually. Examples include cross-platform audience syncs, recurring data quality checks, campaign launch validations, reverse ETL into CRM or ad platforms, long-running backfills, budget pacing checks, and custom reporting jobs.

What you can do

• Describe a workflow in plain language and have the AI Agent build it.
• Run pipelines manually when you need an immediate result.
• Schedule recurring runs with cron-based automation.
• Connect pipelines to Improvado data sources and destinations using saved workspace connections.
• Use durable state for cursors, bookmarks, and incremental processing.
• Track every run with status, timing, output, errors, and activity timeline.
• Publish artifacts such as reports, extracts, or debug files for later download.
• Pause, resume, edit, or archive pipelines from the Custom Pipelines page.

When to use it

Use Custom Pipelines for workflows that combine data movement, transformation, validation, and external actions. A good fit is any process where the team can clearly describe the inputs, business rules, and expected output, but the workflow is too custom for a fixed UI wizard.

Typical use cases:

• Backfill 12 months of spend or conversion data with resumable daily batches.
• Sync audiences from a warehouse or CDP into Meta Ads, Google Ads, TikTok, or LinkedIn.
• Check marketing tables for freshness, missing data, or broken naming rules on a schedule.
• Push attribution or lifecycle metrics back into HubSpot, Salesforce, or other business tools.
• Validate campaign briefs, UTMs, landing pages, and tracking before launch.
• Generate recurring reports or files and publish them as pipeline artifacts.

Each of these is written up with its concrete flow, the parameters that matter, and the gotchas, in Custom Pipeline use cases.

Where it fits

Custom Pipelines sit alongside two neighbouring capabilities, and the fastest way to build one is to use them in order:

You want to…	Use
See or change something in a platform right now, once	Discovery API in chat
Load a large dataset on a schedule for reporting	Extract & Load
Repeat a multi-step process — read, decide, act, report — on a schedule	Custom Pipelines
Get alerted when a metric in a connected source drifts	Discovery API governance rules

Prototype in chat first. Ask the Agent to pull or change what you need through the Discovery API, confirm the result is exactly right, then ask it to turn that into a pipeline. The pipeline reuses the same connections and the same request shape, so a request that worked in chat works on a schedule.

How it works

A pipeline is created through Improvado Agent. The Agent writes the workflow, configures the required connections, and saves the pipeline in the workspace.

Pipelines run on Improvado's durable workflow runtime, which is what makes them safe to schedule: each step is isolated and retried independently, long runs survive infrastructure restarts, and every execution keeps a full activity timeline. Pipelines created before this runtime shipped continue to run as they are and can be maintained in place.

Credentials are not hardcoded in pipeline code. Connections are declared at the pipeline level and resolved securely at runtime. The workflow receives tenant-scoped access to the selected data sources, destinations, Improvado storage, and temporary file or artifact storage.

How to use

1. 1Open Custom Pipelines.
2. 2Click New Pipeline.
3. 3Describe the workflow to Improvado Agent: what data to use, what should happen, how often it should run, and what output you expect.
4. 4Review the generated pipeline overview, configuration, connections, and schedule.
5. 5Run the pipeline manually for the first test — on a small slice of data.
6. 6Check Run History for status, timeline, output, errors, and generated artifacts.
7. 7Use Edit with AI to adjust logic, parameters, schedule, or connections.
8. 8Turn the schedule on once a manual run has produced output you are happy with.

What users see

The Custom Pipelines list shows all available pipelines in the workspace, including status, category, schedule, last run, and creator.

Each pipeline has a detail page with:

• Overview: summary, status, schedule, category, and high-level configuration.
• Configuration: visual workflow graph, step details, and source code.
• Run History: recent executions, live status, duration, timeline, output, logs, metrics, and errors.

Everything on that page — schedules, run history, artifacts, editing and pausing — is covered in Pipeline runs, schedules & artifacts.

Good prompt examples

“Create a daily data quality pipeline that checks yesterday’s Meta Ads and Google Ads spend tables for missing rows, stale data, and zero-spend anomalies. Send a summary artifact with the failed checks.”

“Build a weekly reverse ETL pipeline that reads high-LTV customers from Improvado Storage and pushes audience updates to Meta Ads and Google Ads.”

“Create a campaign launch validation pipeline that reads a Google Sheet with campaign briefs, checks naming conventions and landing page tracking, then returns a report with pass/fail results.”

Availability

Custom Pipelines are enabled per workspace. If you don’t see the Custom Pipelines area, contact your Improvado representative. Resource limits, the credential model, and how pipeline runs relate to AI Agent credits are covered in Limits & availability.