The win-back offer went out to someone who'd already resubscribed.
A batch job with a delay sent an offer to someone who'd already come back. Slightly awkward fixed by checking live subscription status right before every send.
→ Batch jobs and real-time decisions don't always mix well.
Pulling the live subscription check right before the send stops duplicate offers from slipping through. It keeps the batch and real time parts from stepping on each other.
n8n is absolute gold for orchestrating lead pipelines like this! Connecting Gmail parsing with LLM qualification saves teams dozens of hours weekly. As someone who builds custom agentic lead automation workflows, seeing clean visual architectures like this is super satisfying. Top-tier build, Talha!.
A purchase order arrives by email. 38 seconds later it's registered, stock is checked, the team is notified and the client has a confirmation. Nobody typed anything.
We filmed the PO intake agent in TechFoundry IMS end to end for the first time. Watch it here https://youtu.be/zoVYPD8qpCs
Email comes in, the agent reads the PDF line by line and matches every line to the catalog, the PO gets registered with a status timeline, and an acknowledgment goes back to the client with the same lines on it.
The boring parts are the ones that made it usable. Only approved senders get in. Every email in and out is logged. And the agent never touches stock levels, it registers and notifies, people decide.
The part that took longest wasn't the reading. It was the matching. A supplier's PDF never uses your part numbers, so "resolve to catalog" is where most of the real work sits.
If you're still keying POs in by hand, I'm curious what your inbox looks like on a Monday.