New-signup welcome drip
A timed sequence of emails (and optional push notifications) that fires automatically when a new user signs up. Welcome them, walk them through key features, and nudge them at the right moments before they go cold.
The problem this solves
Most users who sign up never come back. Not because your product is bad, because nobody told them the next thing to do. A single welcome email gets a 50% open rate; a drip of three or four gets four times the activation lift. But manually building one means juggling auth events, email templates, schedules, and per-user state.
What you end up with
Every new signup receives a sequence that meets them where they are: an instant welcome, a day-1 "here's how to get value", a day-3 nudge about a key feature, and a day-7 invitation to share or upgrade. The platform tracks delivery and respects unsubscribe, you only describe the message at each step.
How it works
- A new user signs up. The platform records the signup event with a timestamp.
- Immediately: a welcome email goes out with their name, what to try first, and a deep link into your app.
- A scheduled job runs daily, finds users who passed each milestone (24h, 72h, 7d), and queues the next message.
- Each step is its own email (or push). You describe the copy and the trigger, the platform handles delivery, retries, and bounce tracking.
- Users who unsubscribe or complete the activation milestone drop out of the sequence automatically.
Schedule
Daily at 9:00 AM KST (sequence dispatcher)
cron: 0 9 * * *
timezone: Asia/SeoulPrimitives used
The building blocks this recipe composes. Tap any to drill in.
Signup rules & access control
AuthenticationControl who can sign up: open registration, invite-only, email domain allowlists, required email verification. Configured in Auth → Settings, applied automatically across all login methods.
Scheduled jobs (cron)
Scheduled jobsRun code on a schedule, every hour, every Monday morning, the first of the month. Cron jobs are built in: pick a schedule, describe what should happen, and the platform handles dispatching, retries, and authentication. The classic primitive for weekly reports, daily digests, expiration nudges, and any recurring automation.
Outbound email & AI rewrite
Email & pushSending email is built in: both the automatic emails your app sends (like receipts and password resets) and marketing campaigns. AI can rewrite your copy on demand for better results. There's no mail server to set up and nothing to configure; DontCode handles delivery.
Push notifications & in-app notification center
Email & pushPush notifications and an in-app notification center ship with every project. Subscribers self-manage; the platform handles subscription tokens, delivery, and badge counts. No FCM/APNS setup required.
Build this in your project
A ready-to-paste prompt for Insight. Open the App chat in your project and paste this, the build agent does the rest.
Build me a new-user welcome drip sequence. Send a welcome email instantly when someone signs up. Then send three more emails: one at 24 hours with "here's how to get your first win", one at 72 hours featuring one of our key features, and one at 7 days inviting them to invite a friend. Use the user's first name. Drop users from the sequence if they unsubscribe or complete onboarding. Include the right copy for both Korean and English users.Related recipes
Subscription expiration nudge
When a paid subscription is approaching renewal or expiration, automatically remind the customer 7 days out, 3 days out, and 1 day out. Friendly tone for renewals, urgent tone for expirations. Catches churn before the card declines.
Abandoned checkout recovery
When a customer reaches checkout but does not complete the purchase, automatically email them a friendly reminder within a few hours, and a follow-up the next day. Typical recovery rate: 10-20% of abandoned orders convert.
Weekly admin report
Send yourself (or your team) an automated Monday-morning email summarizing last week: signups, active users, revenue, top performers, and survey results. Archives a copy to private storage so you build a running history.