All templates

Automated PoultryPlan Hatchery Delivery Confirmations

When a new chick delivery is logged, WebRun checks the received count against the hatchery's manifest in PoultryPlan, drafts a confirmation with any DOA credit request for your review, and posts the receiving summary to Slack.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Runs the moment a delivery is logged WebRunorchestrates each step
1 PoultryPlan log the delivery count
2 Gmail draft the hatchery confirmation
3 Slack post the receiving summary
In short

How do I confirm a chick delivery against the hatchery manifest without manual paperwork?

When your crew logs a new chick delivery, WebRun checks the received count against the hatchery's manifest inside PoultryPlan and notes the DOA count and the house. It drafts a delivery confirmation and, if DOA is above your threshold, a credit request in Gmail, leaving it unsent for your review, while posting the receiving summary straight to Slack.

  • Every delivery is checked against the manifest at receiving, not discovered short weeks later
  • A DOA credit request is drafted the same day instead of being missed entirely
  • The receiving channel has a delivery summary before the crew finishes placement

Built for broiler growers · pullet growers · hatcheries · poultry integrators

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.poultryplan.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    PoultryPlan - log the delivery count
    poultryplan.com
    WebRun in PoultryPlan: log the delivery count
    WebRun opens PoultryPlan to log the delivery count.
    • Open the new delivery entry in PoultryPlan
    • Compare the received count against the hatchery's manifest count
    • Note the DOA count and the house it was placed in

    Done when The delivery is logged with received count, DOA count, and house.

  3. 2
    Gmail - draft the hatchery confirmation
    gmail.com
    WebRun in Gmail: draft the hatchery confirmation
    WebRun opens Gmail to draft the hatchery confirmation.
    • Draft a delivery confirmation to the hatchery with the received and DOA counts
    • Include a credit request if DOA is above your agreed threshold
    • Leave the email as a draft for you to review and send

    Done when A draft confirmation is waiting in Gmail for your review.

  4. 3
    Slack - post the receiving summary
    slack.com
    WebRun in Slack: post the receiving summary
    WebRun opens Slack to post the receiving summary.
    • Post the delivery summary to the receiving channel
    • Flag the house if DOA came in above your agreed threshold
    • Tag the flock supervisor for placement follow-up

    Done when The receiving channel has today's delivery summary.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.poultryplan.com
ScheduleRuns automatically on this cadence
Runs the moment a delivery is logged
DeliveryHow each run's result reaches you
Receiving summary · Slack
OutputWhat each run produces - A delivery summary with received count, DOA count, and house, plus a draft hatchery confirmation waiting for your review.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it request a credit from the hatchery on its own?

No. WebRun only drafts the confirmation and credit request in Gmail. It stays a draft until you review the counts and send it yourself.

How does it know the DOA threshold that matters?

You set the threshold once. Any delivery with a DOA count above that number gets flagged in the draft and in Slack. Below it, the delivery is simply logged.

What if the received count does not match the manifest?

It calls out the difference in both the draft email and the Slack summary, so a shortage or overage gets noticed at receiving, not weeks later.

Keep going

Related templates

Automated PoultryPlan Biosecurity Checklist Reminders
Every morning, WebRun checks PoultryPlan for any house missing yesterday's biosecurity checklist, such as shower-in logs or vehicle disinfection, pings the crew in Telegram, and logs completion rates to a Google Sheet.
PoultryPlan›Telegram›Google Sheets
Automated PoultryPlan Cull Rate Anomaly Reports
Every night, WebRun compares each house's cull rate in PoultryPlan against its normal range by age and breed, logs the trend to Excel, and posts any house running above normal to Slack for a same-night check.
PoultryPlan›Excel›Slack
Automated PoultryPlan Egg Production Reports
Every morning, WebRun pulls yesterday's egg counts and hen-day production from PoultryPlan, logs the totals to a Google Sheet, and emails you a short summary so you know how every house laid before you are on site.
PoultryPlan›Google Sheets›Gmail

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us