Alerting
Farm alerts, posted straight into your Teams channel.
Your operation runs on Microsoft. The crew schedule is in Teams, the maintenance chatter is in Teams, and the dissolved oxygen alert is in an inbox nobody has open in the greenhouse. The alert did its job. The delivery did not.
An alert that arrives outside the team’s working surface has to be found. An alert that arrives inside it just has to be read. For organizations standardized on Teams, that difference is measured in response time.
How it actually works
FarmHub posts alert cards into a Teams channel through an incoming webhook URL that you create and control.
- Conditions checked every five minutes. FarmHub evaluates alert conditions on a five-minute cycle. When a threshold trips, a card posts to your channel summarizing the alert: what fired, where, and at what severity.
- Alerts, resolutions, and corrective actions all post. The channel hears when an alert raises, when it resolves, and when a corrective action is closed out, so the team sees the whole loop, not just the alarm.
- A webhook URL is the whole connection. You paste the incoming webhook URL from your Teams channel into FarmHub. No OAuth dance, no tenant-wide app approval. The channel owner can set it up directly, as long as the organization’s Teams admin allows connectors, which is the default but can be restricted by IT policy.
- Failures are read correctly. Teams has its own success signal, and FarmHub interprets it properly, so a deleted webhook registers as a delivery failure you can see rather than a silent drop.
Email and push notifications are already built into FarmHub. Teams delivery is for putting the alert where a Microsoft-based crew already looks.
WHAT YOU CAN COUNT ON
What you can count on
What you are actually getting:
- Setup in minutes, revocable in seconds. The connection is one webhook URL. Delete the webhook in Teams or hit the kill switch in FarmHub and delivery stops instantly.
- Delivery retries with backoff. Transient failures retry automatically. An alert does not disappear because Teams was briefly unreachable.
- Severity carried through. FarmHub alert severities ride along on the card, so a high-severity excursion reads differently from an informational note.
- Hash-chained audit rows. Every delivery attempt is recorded in a tamper-evident audit log, so you can prove what was sent and when.
What we do not do
Where this integration stops:
- FarmHub does not read anything from Teams. The flow is one-way, outbound only.
- A channel post does not wake anyone at 4 a.m. For alerts that must escalate to a human, pair Teams with our PagerDuty or Twilio SMS integrations.
- FarmHub does not manage Teams users, channels, or permissions.
Setup, honestly
You need a Teams channel and permission to add a connector to it.
- In your Teams channel, add an Incoming Webhook connector and copy its URL.
- In FarmHub, open Integrations, choose Microsoft Teams, and paste the webhook URL.
- Send the built-in test card and confirm it appears in the channel.
- Pick which alert severities should post, and let the five-minute checks do the rest.
Questions farmers ask
Does FarmHub need admin approval in our Microsoft tenant?
No. The connection is an incoming webhook URL created on the channel itself. Anyone with permission to add a connector to the channel can set it up.
How fast do alerts arrive?
Alert conditions are checked every five minutes. When one trips, the card posts immediately, with automatic retries on transient failures.
What appears in the channel?
A card summarizing each alert raised, each alert resolved, and each corrective action closed, with the severity carried through.
What happens if someone deletes the webhook?
Deliveries fail visibly rather than silently. FarmHub records the failure, and your built-in email and push notifications continue independently.
Can FarmHub read our Teams messages?
No. FarmHub only posts to the webhook URL you provided. It has no read access to your Teams environment at all.
READY FOR THE NEXT SHIFT
Put the alert in front of the team
Paste one webhook URL and the next threshold breach posts itself into the channel your organization already runs on. Five minutes of setup, no admin ticket.
Start free