Your project coordinator opens Procore on Monday morning and spends the first two hours of her day doing the same thing she did last Monday: going through every active project's submittal log, cross-referencing return dates, flagging overdue items, and drafting reminder emails to architects and engineers who haven't responded. On a 4-project job, that's 5–8 hours a week. Every week. Nothing gets built faster because of those hours.

We built a workflow in n8n that does all of it automatically — pulling live data from Procore's API, flagging overdue submittals, sending reminder emails to responsible parties, and keeping your project manager's Slack channel updated without anyone touching a spreadsheet.

Here's exactly what we built and how to replicate it.

The Pain Every Project Coordinator Knows

Procore's submittal tool is solid. The problem isn't the tool — it's the manual overhead around it.

Every week, someone on your team is doing this work by hand:

• Pulling up the submittal log for each project
• Identifying items that are past their required return date
• Drafting follow-up emails to the architect or engineer of record
• Updating the master log when submittals come back (approved, approved as noted, revise and resubmit)
• Notifying the relevant sub that their submittal was returned and what the status is

On a single project with 60–80 line items, this is manageable. On three active jobs simultaneously, it becomes a part-time position. And when a submittal sits unanswered at the architect's office for 3 weeks because nobody caught it — the cascade effect hits schedule, materials procurement, and eventually your margin.

What the Automation Does

The workflow we built handles four things:

1. Daily overdue check — Every morning at 7 AM, n8n pulls the current submittal log from Procore via API. It filters for items where the required_on_site_date or due_date has passed and the status is still "Submitted" or "Under Review."

2. Automated follow-up emails — For any overdue item, n8n generates and sends a follow-up email to the responsible party listed in Procore. The email includes the submittal number, spec section, number of business days overdue, and the required-on-site date. No copy-paste, no drafting.

3. PM Slack alert — A daily digest goes to your project manager's Slack channel with a clean list of every overdue submittal across all active projects: who's responsible, how many days overdue, what's at risk on the schedule.

4. Status update notifications — When a submittal status changes in Procore (approved, returned for revision, rejected), n8n fires a notification to the subcontractor who submitted it. They know immediately without waiting for someone to call them or scan their email.

The Build: Step by Step

This workflow connects n8n to Procore's REST API. You'll need a Procore account with API access (available on most paid plans) and an n8n instance (cloud or self-hosted).

Step 1: Set Up the Procore Connection in n8n

In n8n, create a new HTTP Request node and authenticate with Procore using OAuth 2.0. Procore's Developer portal at developers.procore.com lets you register your app and get client credentials.

Once connected, test with a simple GET request to /rest/v1.0/projects to confirm you're pulling your project list.

Step 2: Pull the Submittal Log

Add a Schedule Trigger node set to run at 7:00 AM daily (Monday–Friday). Then chain an HTTP Request node calling:

GET /rest/v1.0/projects/{project_id}/submittals

This returns every submittal in the project with fields including status, submitted_at, due_date, required_on_site_date, responsible_contractor, spec_section, and revision.

Run this node for each active project using an n8n Loop Over Items node — pull your project list first, then iterate.

Step 3: Filter for Overdue Items

Add a Filter node after the submittal pull. The logic:

• status is "submitted" OR "under_review"
• due_date is before today's date

This isolates every item that is actively awaiting review and past its deadline. You'll also want to exclude items that already received a follow-up email in the last 3 business days — add a simple Google Sheet or Notion database as a "sent log" and filter against it to avoid spamming architects.

Step 4: Generate and Send Follow-Up Emails

For each overdue item, build your email body using n8n's Set node to construct the message:

Subject: Submittal Follow-Up — [Project Name] / [Spec Section] [Submittal #]

Hi [Responsible Party Name],

We're following up on the below submittal currently under your review:

Project: [Project Name]
Submittal #: [Number] — Rev [Revision]
Spec Section: [Section Number and Name]
Submitted On: [Submitted Date]
Required Return Date: [Due Date] — [X] business days overdue
Required On Site: [Required On Site Date]

Please advise on status. If you need additional information from our team or the submitting contractor, let us know.

[Your PM Name]
[Company Name]

Send via Gmail or Outlook nodes in n8n. If the same architect manages 3 submittals for you across projects, consolidate into one email rather than sending three — add a groupBy step on responsible_party_email before sending.

Step 5: Post the Daily Digest to Slack

Add a Slack node to post a summary to your project management channel. Format it as a clean list:

📋 Daily Submittal Report — [Date]

OVERDUE (requires follow-up today):
• Job 2241 — Spec 08 31 00 Doors, Sub 04, Rev 1 — 9 days overdue (Apex Arch)
• Job 2241 — Spec 26 27 26 Panels, Sub 12, Rev 0 — 4 days overdue (MEP Engineers)
• Job 2253 — Spec 07 21 00 Insulation, Sub 08, Rev 2 — 6 days overdue (Smith & Co)

RETURNED THIS WEEK (subs notified):
• Job 2241 — Spec 09 29 00 Drywall, Sub 06 — Approved As Noted
• Job 2253 — Spec 03 30 00 Concrete, Sub 02 — Revise and Resubmit

The PM sees the whole picture without opening Procore. The subs get their status notifications automatically. Nobody has to ask.

Step 6: Set Up the Status Change Trigger

For real-time sub notifications, set up a Procore webhook that fires when a submittal status changes. In Procore's API settings, register a webhook for the submittals.updated event pointing to your n8n webhook URL.

When n8n receives that trigger, it checks whether the status changed to a "final" state (approved, approved as noted, rejected, revise and resubmit), pulls the submitting contractor's contact info from Procore, and sends a direct email notification:

Subject: Submittal Returned — [Project Name] Submittal #[X], Spec [Section]

Your submittal has been returned with the following status: [Status]

Submittal #: [X], Rev [N]
Spec Section: [Number and Name]
Returned by: [Reviewer Name]
Action required: [Approved — proceed / Approved As Noted — review comments / Revise and Resubmit — address comments and resubmit]

See attached for the stamped submittal in Procore.

Setup time for all six steps: 4–6 hours, assuming you have API credentials and an n8n instance running. Most of that is the initial Procore API setup and testing your first project's data pull.

What This Saves

On a 3-project job, this workflow replaces roughly 5 hours of manual tracking per week. That is 20 hours a month your project coordinator can put toward actual project coordination instead of chasing paper.

More importantly, it closes a specific margin leak: architects don't go 3 weeks uncontacted on an overdue submittal. Your PM knows within 24 hours if something is sitting. Materials that are schedule-critical get flagged before they become a delay claim.

One GC we worked with was averaging 11 business days overdue per flagged submittal before the automation ran. After 60 days of automated follow-ups, that average dropped to 4 business days. On a $5M commercial job, faster submittal turnaround reduces float risk and gives your PM something to point to when the owner asks about schedule confidence.

The Quick Win — and What Comes Next

This automation is completable in under 6 hours and runs on n8n's Cloud Starter plan at €20/month plus your existing Procore subscription. No IT department, no custom development, no ERP changes.

This is step 1. When you're ready to connect your submittal tracking to your materials procurement system, automate RFI responses, and tie your schedule float to your change order risk — that's where architecture matters. A single workflow is a quick win. A connected system is a competitive advantage.

Book a discovery call at cloudbeast.io/schedule and we'll map your current process in 30 minutes.