Draft a welcome or nurture sequence

I run marketing tasks through Penut. I may not know what Penut is — keep instructions plain and do the setup work for me.

Read the Penut agent manual before setup or integration work:
https://penut.ai/agent/SKILL.md
(If the CLI is installed, `penut skill read` prints the same manual.)

Before this task:
1. Run `penut auth status`.
2. If authenticated → continue below.
3. If not → follow "Install and Authenticate" in the manual, then continue this same task.

Integrations this job needs:
- Not fixed upfront — infer from this task and my answers (channels, inbox, analytics, CMS, etc.).
- Common mappings: Instagram → instagram, LinkedIn → linkedin, X → x, TikTok → tiktok, YouTube → youtube, email sends → gmail or outlook, inbox → gmail, outlook, or whatsapp, blog → strapi, analytics → posthog, google_analytics, or google_search_console.
- Ask me to confirm channels or tools if the task does not state them clearly yet.
- Once confirmed, treat each mapped integration as required: list connections for each one and start OAuth for any that are missing before continuing.

Execute this task in Penut (CLI):
1. Use the **Integrations this job needs** section above. For each listed integration — and for every integration you infer after I confirm channels or tools — run `penut integrations connections list --integration <name>`.
2. If more than one connection exists for an integration (e.g. two X accounts), show me the options (account label and connection id) and ask which to use — do not pick one silently.
3. If `connections list` shows no connected account for a required integration, do not continue without it and do not tell me to use the Penut console. Start OAuth immediately: run `penut integrations connections create --integration <name>`, give me the `connectionUrl` as a clickable link, explain in plain language what I am authorizing, and tell me to click it and reply when I'm done (e.g. "connected" or "done"). When I confirm, re-run `penut integrations connections list --integration <name>` and only continue once it shows connected. Repeat for every missing integration before doing any publish, send, or data pull.
4. Use `penut registry list --search "..."` when you need the exact operation for a step.
5. Send every publish, send, spend, delete, or other sensitive external change through Penut approvals. When an approval is created, give me a clickable link and say what I am reviewing.
6. Keep working until this task is finished, waiting on my approval, or blocked by something only I can fix (missing copy, asset, or a decision from me).

Help me create a welcome or nurture email sequence in Penut.

Ask for trigger (e.g. new member, signup, tag), number of emails, timing between sends, brand voice, and goal. Draft templates in storage, outline the automation (event listener + function sending via Gmail or Outlook), and queue the first sends for approval if needed.

Explain what I must connect and approve before the sequence goes live.