All jobs

Which Leads Came In Through Each Client's Website This Week? A Web Design Agency's Netlify Forms Digest

A web design agency's agent reads last week's Netlify Forms submissions on every client site and writes each client a lead digest for the account manager to send.

Run this on RushOpens the console with this prompt ready to send. Connect Netlify there first.

What the agent does

This is for a web design agency that builds marketing sites for local businesses, such as builders, caterers and law offices, and hosts them on the agency's Netlify team. Each site's contact and quote forms use Netlify Forms. Clients want to know what came in, and account managers export submissions site by site to tell them. The agent does that every Monday. Someone at the agency connects Netlify once with POST /me/connections {"type": "mcp", "name": "netlify", "url": "https://netlify-mcp.netlify.app/mcp", "auth": {"mode": "oauth"}}, the address Rush lists; Netlify says connections to it keep working and names https://mcp.netlify.com/mcp for new ones.

Netlify's server groups its operations by area, with one tool that reads (netlify-project-services-reader) and one that writes (netlify-project-services-updater), each taking the name of an operation. The run uses get-projects with the agency's team slug for every site id, then get-forms-for-project on each site for its forms and their submission counts. For each form with submissions it calls manage-form-submissions with action set to get-submissions and the form id, paging with limit and offset, and keeps the submissions that arrived in the last seven days.

For each client it writes a digest: how many submissions each form got, then each lead in one line with the person's name, how they asked to be reached, what they asked for in their own words, and which form they used. Submissions that look like junk, such as a message that is only a link, an empty message, or the same text sent to several clients' forms within minutes, go in a separate list at the end rather than being dropped, because the account manager decides what is spam.

manage-form-submissions sits in the updater tool because the same operation can also delete a submission permanently with delete-submission. The prompt forbids that action, along with update-forms and every other write, so the agent reads the forms and changes nothing on any site.

Start it with one API call

POST https://api.phoenix.so/o/{org}/sessions with this body:

{
  "agent": "claude",
  "input": "Write last week's lead digests for our client sites on Netlify, for submissions from 2026-11-09T00:00:00-05:00 to 2026-11-16T00:00:00-05:00. Run get-projects with team slug <team slug>. For each site run get-forms-for-project, and for each form with submissions run manage-form-submissions with action get-submissions and that form id, paging with limit and offset until submissions are older than the window. For each site with submissions in the window, write leads/<site name>.md: a count per form, then one line per lead with name, email or phone as given, what they asked for in one sentence of their own words, and the form name. Put submissions whose message is empty, is only a link, or repeats the same text across sites in a 'Possible junk' section at the end of that file. Write leads/index.md listing every site with its count, including sites with none. Never use action delete-submission, never run update-forms, and change nothing on any site.",
  "connections": [
    "netlify"
  ]
}
  1. Get an API key. In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
  2. Send the request. POST the body in request.json to https://api.phoenix.so/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
  3. Read what came back. Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.

What comes back

A folder of files comes back as artifacts on the session: one digest per client site and an index that lists every site with its count, so a client with no leads this week is visible too. The result is a short summary for the person who set it up.

The account manager reads each digest before it goes out. They move a junk line back if it was a real enquiry with a short message, remove anything the client should not see, and send it from their own mailbox with a sentence of their own. A site with no submissions for several weeks is worth a look: the form may have been removed in a redesign or form processing may have been turned off for that site, which get-forms-for-project returning nothing would show.

The digests carry people's names and contact details, and so does the session's transcript, which holds what the tools returned. The agency treats both as client data.

Run it on every Monday morning

In the console, a Project automation with a schedule trigger (0 8 * * 1 in the agency's timezone) can run a saved agent that names the Netlify connection and holds the digest's layout and the junk rules, with a prompt that asks for the previous seven days. With notify_each_run on, the summary reaches the person who set it up as soon as it is done.

An agency that bills lead reporting as a service can start the same request from its own client portal per client, with a request_id that is a UUID v5 of the site and the week so a retry starts no second run, and show each digest in the portal when the webhook arrives.

The use case this job follows, with its automation and trigger: Produce a report or file, no repo.

Why run it on Rush?

Netlify can email each submission as it arrives, which is fine for one site and noise across many. What the client wants is a weekly summary in plain words, and what the agency wants is not to make it by hand. The agent reads every form on every site in one run and writes the same digest each week. The Netlify sign-in stays in Rush's connection, not a personal access token in a script on someone's laptop.

Each run has its own computer, a record of every call it made and its cost, and nothing to clean up afterwards. Because the transcript would show any delete, the agency can see that the agent read the submissions and removed none.

Frequently asked questions

Some clients host their site on their own Netlify account. Does this still work?

Not from the agency's connection, which reaches only the agency's team. Those clients can each connect their own Netlify to an agent the agency makes for them from a template, and the agency runs that agent with the same prompt.

Could the agent email the digest to the client directly?

With a Gmail or Outlook connection that can send, it could, but this setup stops at the file. The account manager sends it, since a weekly email to a client is part of the relationship and a wrong lead or a junk line in it is the agency's embarrassment.

Does the agent delete the junk submissions?

No. delete-submission is permanent, and the prompt forbids it. The junk list is a suggestion for the account manager, who can delete in Netlify after checking.

More Netlify jobs

More jobs like this: Produce a report or file, no repo

Keep reading