> ## Documentation Index
> Fetch the complete documentation index at: https://docs.seekout.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build an outreach flow in Amazon Quick

> Create an Amazon Quick flow that finds the top five SeekOut candidates for a role, retrieves their emails, and saves personalized outreach drafts in Gmail.

Amazon Quick flows turn a repeatable task into a form you fill in once. This guide builds a flow from a single prompt. You type what you're hiring for, and the flow finds the five best-matching candidates in SeekOut, retrieves their email addresses, and saves a personalized outreach email for each one as a draft in your Gmail. The flow drafts only. It never sends anything.

## Prerequisites

* **A SeekOut account.** If you don't have one, [start a free trial](https://www.seekout.com/free-trial/).
* **The SeekOut MCP connector, already set up in Amazon Quick.** Follow [Connectors](https://docs.seekout.com/mcp/connect/amazon-quick.md) first and confirm that Amazon Quick can run a SeekOut search before you build the flow. The flow calls SeekOut through that connector, and Amazon Quick can't attach SeekOut to a flow until the connector exists.
* **The Gmail connector, set up in Amazon Quick and available to you.** The flow uses it to save each email as a Gmail draft. To set it up, follow Amazon's [Gmail integration](https://docs.aws.amazon.com/quick/latest/userguide/gmail-integration.html) guide.
* **Auto-accept for tool calls turned on in Amazon Quick.** The flow makes many SeekOut calls in a row. If Amazon Quick waits for you to approve each call, the flow stalls. See [Turn on auto-accept for tool calls](#turn-on-auto-accept-for-tool-calls).
* **Email credits on your SeekOut account.** Each new email lookup uses one email credit. Addresses you have already retrieved are free. One run of this flow looks up at most 10 people.

> [!WARNING]
>
> Set up and test both connectors before you create the flow. If a connector is missing, Amazon Quick builds the flow without its tools: without SeekOut the search and email steps have nothing to call, and without Gmail the drafts are never saved.

## Turn on auto-accept for tool calls

Before you run the flow, turn on auto-accept for tool calls in Amazon Quick so SeekOut and Gmail calls run without asking you to approve each one. The flow makes a dozen or more calls per run. If a call waits for approval, the flow stops there.

The SeekOut tools this flow uses only read data and retrieve contact details. None of them changes anything in SeekOut, and email retrieval does use email credits. The flow uses the Gmail connector only to create drafts. It never sends them; you review and send each one yourself.

## Create the flow

**1. Paste the prompt**

In Amazon Quick, open **Flows**, choose to create a flow, and paste this prompt into the description box:

```text theme={null}
Create a flow that takes a job description from the user, uses my SeekOut MCP connector to find the top 5 matching candidates and retrieve their emails, then uses my Gmail connector to save a personalized outreach email for each one as a Gmail draft. Never send email.

Steps:
1) User input: "What are you hiring for?"
2) Find and rank candidates with SeekOut. Keep the best 10 and, for each, note one specific thing they did (a project, product or result) that fits the role.
3) Start email lookups: call get_emails with SeekOut for the top 5. Lookups run in the background and often come back as "processing". Do not wait or call check_contacts in this step.
4) Write a draft email for each of the top 5. Each email opens with a specific compliment about something the candidate did, then explains in 1-2 sentences how that fits the role, then asks for a 15-minute chat. Under 120 words, subject of 8 words or fewer. Use only standard keyboard characters: no em dashes, curly quotes, emoji or special symbols.
5) Check emails: call check_contacts once. For each candidate whose lookup finished with no email, replace them with the next-ranked candidate (ranks 6-10), call get_emails for those backups, and write their drafts the same way. Leave anyone still processing as they are.
6) Check emails again: call check_contacts once. Mark anyone still processing as EMAIL PENDING. Mark anyone whose lookup finished with no email as NO EMAIL, and replace their draft with a short LinkedIn message. Never guess an email address.
7) Save each email as a draft with the Gmail connector (Create Draft), addressed to the candidate's email. For EMAIL PENDING candidates, save the draft with no recipient. Do not save drafts for NO EMAIL candidates. Never send.
8) Show a table of the 5 candidates (name, title @ company, email or status, profile link, and whether a Gmail draft was saved) and each draft under the candidate's name.
```

Choose **Generate**. Amazon Quick creates a flow with eight steps.

Check that starting the email lookups, writing the drafts, and the two email checks (steps 3 to 6) stayed separate steps. The flow doesn't pause between tool calls, so the time spent writing drafts is what gives SeekOut time to finish the lookups. If Amazon Quick merged them, split them back out.

**2. Turn on auto-accept**

Make sure [auto-accept for tool calls](#turn-on-auto-accept-for-tool-calls) is on.

**3. Run it**

Run the flow and answer the input with the role you're hiring for, for example:

Senior software engineer in Seattle, AI/ML domain, agentic experience.

Senior software engineer in Seattle, AI/ML domain, agentic experience.

You get a table of five candidates and their drafts. The emails are waiting in your Gmail **Drafts** folder for you to review and send.

## How email retrieval works

SeekOut retrieves emails in the background, and a lookup can take a minute or more. A flow can't pause and wait, so checking again right away only returns "processing" again. Instead, the flow starts the lookups first, writes the drafts while SeekOut works, and only then checks for results:

1. Step 3 starts the lookups for the top five candidates.
2. Step 4 writes their drafts. This takes long enough for most lookups to finish.
3. Step 5 checks the results, starts lookups for backups to replace anyone without an email, and writes the backups' drafts.
4. Step 6 checks once more.

Anyone still processing at the final check is marked **EMAIL PENDING**. They keep their draft, saved with no recipient, and you can check their email in SeekOut later. A candidate counts as having no email only after their lookup has finished.

## When a candidate has no email

Not every profile has an email on file. That is a normal result, not an error, and the flow handles it:

1. It looks up emails for the top five candidates.
2. At the first check, it replaces each one whose lookup found no email with the next-ranked backup (ranks 6 to 10).
3. Anyone still without an email at the final check is marked **NO EMAIL** and gets a short LinkedIn message in the results instead of a Gmail draft.

The flow never guesses an address from a name pattern. It uses only addresses SeekOut returns.

## Troubleshooting

| Symptom | What to check |
| - | - |
| The flow has no SeekOut tools | The connector isn't set up yet, or it isn't turned on for the flow. See [Connectors](https://docs.seekout.com/mcp/connect/amazon-quick.md). |
| Most candidates end up EMAIL PENDING | The checks ran before SeekOut had time to finish. Make sure steps 3 to 6 are separate steps in this order: start lookups, write drafts, check, check again. |
| A few candidates are still EMAIL PENDING | Their lookup is taking longer than usual. Run the flow again later. Addresses that already came back are free the second time. |
| The flow stops partway and waits | A tool call is waiting for approval. Turn on [auto-accept for tool calls](#turn-on-auto-accept-for-tool-calls). |
| "Save Drafts to Gmail ... does not have valid access permissions. Contact your administrator to enable access." | If you just added the connector, hard refresh the Amazon Quick page (Cmd+Shift+R on Mac, Ctrl+Shift+R on Windows) and run the flow again. Otherwise you don't have access to the Gmail connector the flow uses, or you haven't signed in to it yet. Ask whoever published the connector to give you access, or connect Gmail yourself, then open the flow's save-drafts step and pick that connector. See Amazon's [Gmail integration](https://docs.aws.amazon.com/quick/latest/userguide/gmail-integration.html) guide. |
| No drafts appear in Gmail | The Gmail connector isn't set up, you didn't allow every Google permission, or **Create Draft** isn't available on the connector. Check that Amazon Quick can create a Gmail draft on its own, then run the flow again. |
| Google says the app is blocked | Your Google Workspace administrator restricts third-party apps. Ask them to allow Amazon Quick. |
| An email lookup is refused | Your account may be out of email credits. The response explains why. |

## Extend the flow

Once the basic flow works, edit its steps to add one change at a time:

* Add optional input fields for your company name, signature, and compensation range, and use them in the drafts.
* Prefer a candidate's personal address over one at their current employer.
* Use Outlook instead of Gmail by swapping the Gmail connector for an Outlook connector in step 5.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.