Prerequisites
- A SeekOut account. If you don’t have one, start a free trial.
- The SeekOut MCP connector, already set up in Amazon Quick. Follow Connectors 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 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.
- 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.
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: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 is on.
3
Run it
Run the flow and answer the input with the role you’re hiring for, for example: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.
Senior software engineer in Seattle, AI/ML domain, agentic experience.
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:- Step 3 starts the lookups for the top five candidates.
- Step 4 writes their drafts. This takes long enough for most lookups to finish.
- Step 5 checks the results, starts lookups for backups to replace anyone without an email, and writes the backups’ drafts.
- Step 6 checks once more.
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:- It looks up emails for the top five candidates.
- At the first check, it replaces each one whose lookup found no email with the next-ranked backup (ranks 6 to 10).
- 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.
Troubleshooting
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.