Skip to main content

How to connect a different email to Sequences

Learn how to link a separate email account to your Puck dashboard to manage outreach sequences. This guide walks you through the authentication process and configuration steps to keep your recruiting workflow moving smoothly.

Written by Melisa Cooper

Many companies prefer to standardize candidate outreach by sending sequence emails from a shared team handle—such as hello@company.com, careers@company.com, or no-reply@company.com—rather than an individual recruiter's personal inbox. Connecting a dedicated company-wide email keeps branding consistent and ensures candidate replies are managed in one centralized location.


For the purpose of this guide, I have logged in under my professional email below to demonstrate how you can log in with one profile while connecting a completely different email address to handle your sequences.


🔐 Step 1: Connect Your Email Provider

  1. Go to Sequences > Campaigns in the sidebar menu.

  2. On the Connect your email page, choose your email provider

💡 Note: You must have the active login credentials for the specific email account you wish to connect.

3. Follow the on-screen prompt boxes and check the box giving Puck permission to use your email account to send sequence outreach.


✅ Step 2: Verify Connection & Test Configuration

  1. Once connected, your Sequences dashboard will transform and enable you to create New Sequences.


2. Click Create new sequence to test your setup. 📝


3. Check the From field in the sequence builder to confirm it displays your newly connected email address. 📬


💡 Best Practices

  • Use Dedicated Sending Accounts: Connect a team or recruiting-specific email handle (e.g., careers@company.com or recruiting@company.com) to manage high-volume sequences cleanly.

  • Check Permission Scopes: Ensure your email admin allows third-party API access if using an enterprise Google Workspace or Microsoft Outlook account.

  • Multiple users can enable the same shared company email to send sequence.s

Did this answer your question?