wf-distribution-trial-connect
Every new Distribution.ai trial in Loops becomes a LinkedIn connection request from Yuliya. No email. No ICP gate. They already signed up.
Anyone who starts the 15-day Distribution.ai trial. About 10–20 a week. Not the old failed-trial revival list.
Her LinkedIn. Connection request plus follow. Julia Gardiner is Foundation sales and is not this lane.
Loops already emails the trial. This machine only does LinkedIn. No ICP classify — they already signed up.
Where this happens — Cloudflare cron + Loops
Every morning at 9:00am Chicago it looks for trial signups since the last run. Email and name come from Loops.
Loops’ public API finds one contact at a time — it does not list “everyone new today.” Before we build: confirm a webhook on trial start, a Zap into our worker, or a list export we can poll.
Where this happens — worker
No new trials today → stop. Nothing is sent. Same person is never processed twice.
Where this happens — FullEnrich
Reverse-email lookup, the same path Subscriber Miner already uses. Skip @distribution.ai and anyone already in this log.
Where this happens — worker + Aimfox
No LinkedIn, no profile photo, or already locked in another Aimfox campaign → do nothing. Dead end. Those people stay in Loops email only.
Where this happens — Aimfox
Connection request plus follow. One campaign. No Instantly. Add the row to the Distribution dashboard the same day it goes live.
This map is the plan. The worker is not built yet. Aimfox API create is a blank shell — the team pastes the connect note in the UI before launch.