# Failed automation review intro email | SourceX

Canonical: https://refer.sourcex.si/resources/failed-automation-review-introduction-email
Last updated: 2026-11-04

Write to the client's decision-maker in three short paragraphs: what the failed automation review found about where repairs are recorded, who can decide and what SourceX does, and a plain disclosure followed by a metadata-only ask. The draft below is ready to adapt. The annotation after it explains each sentence and what must stay out: no run logs, no error messages, no customer names, no exported history and no value estimate.

It is part of the [failed automation review guide for workflow automation agencies](/guides/moment-failed-automation-review-workflow-automation-agencies). Most agencies reach this email after the [failed automation review archive context checklist](/resources/failed-automation-review-archive-context-checklist) has settled what exists and when cleanup is due.

## Send it only after these four answers

The email describes facts the client gave you. If any of these four is missing, the draft is not ready.

| Answer you need | Who gives it | Why the email depends on it |
|---|---|---|
| The owner agreed to an introduction, after you disclosed your interest | Owner or CEO | Without it, the email is a cold pitch about someone else's records |
| Where repairs are recorded and by what key | Operations, finance or sales operations lead | It is the email's only factual claim |
| Roughly how far back the business-system history goes | Same leads or IT | It gives shape without content |
| The name and title of the person who can authorize licensing | Owner | The email goes to them, not to the automation admin |

Also confirm you have signed the Channel Partner Agreement. It comes before any introduction is submitted.

## Ready-to-adapt draft for an automation client

Illustrative. Bracketed placeholders are filled only with what the client told you.

> **Subject:** Introduction: [Company] and SourceX, automation repair history
>
> Hi [Decision-maker name],
>
> During our review of [Company]'s [order-to-invoice] automations, your team explained that when a run fails, the fix is usually made in [the ERP and the helpdesk], and that about [half] of those repairs reference the [order or ticket] number, so the failure and the human correction can be matched. That history goes back roughly [number] years in the business systems.
>
> You are the person who can decide whether that record of errors and corrections is worth a conversation with SourceX, which licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout. I have not exported, copied or shared any run history or system records.
>
> For transparency, I am a SourceX referral partner. If a qualifying license completes, SourceX may pay me a reward from its own funds; it is never deducted from what [Company] is paid. Would a 20-minute call about which systems, which years and who owns them be useful before the old workflows are cleared?
>
> [Your name]

## Why each line is worded this way

Each row is one sentence of the draft. The right-hand column lists what to keep out of it.

| Line | Purpose | Keep out of it |
|---|---|---|
| Subject line | Names both parties and says "repair history" rather than "automation data", the half the email is about | "Opportunity", a dollar figure, or "time-sensitive" |
| "During our review of [Company]'s [order-to-invoice] automations..." | Places the email inside a project the recipient approved | Findings about specific broken workflows or blame for failures |
| "...the fix is usually made in [the ERP and the helpdesk]..." | States where repairs live, which is the core of the question | Names of the clerks or managers who made the fixes |
| "...about [half] of those repairs reference the [order or ticket] number..." | Says how the two halves link, in a rough proportion the client gave | A precise count you computed from logs |
| "...goes back roughly [number] years..." | Gives the depth of history without content | A year range you guessed |
| "You are the person who can decide..." | Confirms authority and hands over the choice | Any suggestion that the company already qualifies |
| "...SourceX, which licenses approved business data..." | One accurate sentence about SourceX | Claims about buyers, prices or demand for automation logs |
| "I have not exported, copied or shared..." | Confirms the records stayed with the company | Any sign that you hold a sample error, screenshot or export |
| "For transparency, I am a SourceX referral partner..." | Discloses your interest and that SourceX funds the reward separately | The reward amount, or wording that implies the company pays it |
| "Would a 20-minute call... before the old workflows are cleared?" | A small metadata-only ask tied to the client's own cleanup event | A request for logins, exports, run IDs or sample records |

### The run half and the repair half

The email deliberately leads with the repair half. Platform run history is short-lived by design: Zapier's help says it can only promise up to 60 days of run data in Zap history, and Microsoft documents that Power Automate keeps flow run data for 28 days by default. The corrections people made in the ERP, CRM or helpdesk follow those systems' own retention rules, which may be much longer, so they are often what the decision-maker can still choose about. The [integration error-handling records](/data-types/integration-error-handling-records) page describes that systems-side record in general.

### "Retried after a change" is not the same as "replayed"

If the client retried runs, ask how before writing. n8n, for example, can retry a failed execution with the original workflow or with the currently saved one, so a retry after a change carries part of the fix in the workflow itself. A plain replay with nothing corrected shows only that someone pressed a button. Describe only what the client says was actually fixed.

## Words to strike before sending

Read the finished draft once more and remove anything on this list.

- **Error messages or step names copied from a run.** Even a single error text can carry customer or system details.
- **Screenshots of error queues.** They move company information outside its systems without authority.
- **"We can export this for you."** It offers a data transfer that is not yours to offer.
- **Agency marketing.** The email is about the client's records, not the agency's services.
- **Any statement about value.** Whether a buyer wants a particular company's repair history is known only after SourceX reviews it.

For different openings, try the [introduction email builder](/tools/introduction-email-builder) or the [client introduction email templates for agency owners](/resources/client-introduction-email-templates-for-agency-owners). If the client tried to sell data before and it stalled, [why data monetization failed](/questions/data-monetization-failed) is useful context to keep handy, but not to paste into the email.

## Recipient, fit and what SourceX decides later

The recipient is the person who can authorize a licensing discussion: the CEO, who in an owner-run company is usually the owner. The company usually owns its business-system records; the agency holds only delegated access to the automation platform. Customer contracts and privacy obligations may limit reuse, and that is the company's counsel's call.

Check fit before sending: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

| Topic | What your email can say | What SourceX settles later |
|---|---|---|
| Records | Where repairs are recorded and how they link to runs | Whether those records match current demand |
| Ownership | That the company owns its business systems, as the owner said | The rights review, including customer and privacy terms |
| Authority | The named decision-maker | Dataset scope and de-identification |
| Money | That any reward is funded separately by SourceX | Any offer to the company and any reward to you |

Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. Nothing is payable on the email, a meeting or a signature alone, as the [rewards page](/rewards) explains. The guide to [exception handling data for AI agents](/guides/exception-handling-ai-agents-data) explains why error-and-correction records draw interest in the first place.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the owner has opted in and every placeholder in the draft comes from their team's answers about failed runs and repairs, [register as a partner](/register), confirm fit on [who qualifies](/who-qualifies), and keep the [program terms](/terms) beside you when you send.

## Sources

- https://refer.sourcex.si/terms
- https://help.zapier.com/hc/en-us/articles/8496291148685-View-and-manage-your-Zap-history
- https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-run-issues/missing-runs-or-triggers-history-for-a-flow
- https://docs.n8n.io/workflows/executions/single-workflow-executions/
