Creator Contact Database Prompts - Build a Creator Contact Database: Prompts for Finding Emails

There is a specific kind of stuck that every creator programme hits: forty names you like and no way to reach any of them. DMs go unread. The contact link goes to a talent agency that never replies. The shortlist quietly becomes a document nobody opens.

A contact database solves it, but only if it holds more than email addresses, and only if you are honest about what it will not do.

What you actually lose at each step

Start with a hundred handles you like. You will not end with a hundred conversations, and planning as though you will is why outreach programmes stall in week two.

Some creators have no public contact path at all. Some route through an agency that filters by budget before it filters by fit. Some have an address that no longer works. Some are reachable but in a language you cannot write well. Every one of those is a normal outcome, not a failure of the tooling.

Design for the leak. A shortlist of a hundred that yields thirty real conversations is a good shortlist. A workflow that assumes a hundred and quietly drops seventy is how a programme gets declared "not working".

The prompt

ROLE
Outreach operations analyst with Favikon MCP access.

VARIABLES
{{LIST}}         = Q4 France shortlist
{{MY_LANGUAGES}} = English, French
{{CATEGORY}}     = project management software
{{MAX_TOUCHES}}  = 3

TASK
For every creator in {{LIST}}:
1. Find the reachable contact paths.
2. Name the best first channel and say why.
3. Record what I need in order to write to them: main topics,
  two recent posts worth referencing, audience country,
  posting language, and any brand in {{CATEGORY}} they have
  already worked with.
4. Flag anyone with no reliable contact path.

OUTPUT
Table — handle | best channel | why | posting language |
needs outreach outside {{MY_LANGUAGES}} | post to reference |
category conflict | reachable yes/no

CONSTRAINTS
- A business contact is still personal data. Record the source
 of every contact detail, and never suggest scraping.
- Never guess an address from a name pattern.
- Where no email exists, route to a DM rather than dropping
 the creator.

QUALITY CHECK
Expect a match rate below 100%. If every row is reachable,
some addresses were inferred rather than found. Ask which.

Step four is the one that saves real time. Knowing which four creators are unreachable stops you writing messages that were never going to land, and lets you replace them while the shortlist is still warm.

Store the context, not just the address

An email address gets you delivery. The context field gets you a reply.

Outreach that references a real recent post outperforms a template by a margin large enough that it is worth building the database around that field rather than treating it as a nice-to-have. The address is the cheap part. What you know about the person is the expensive part, and it is the part that decays, which is why it belongs in a database rather than in the head of whoever did the research.

Write in their language, not yours

Group these contacts by the language they post in. Flag anyone I would need to write to in something other than {{MY_LANGUAGES}}.

A half-English pitch to a French or Dutch creator reads as automated faster than almost anything else you could do. It is a one-prompt check that most programmes skip, and it costs nothing to run.

The compliance part nobody wants to read

If you operate in Europe or contact anyone who does, this section is not optional, and it is the reason a lot of creator outreach quietly becomes a legal problem rather than a marketing one.

• A business contact is still personal data. A creator's professional email is covered by GDPR in the same way any other individual's is. "It was publicly available" is not a lawful basis.
• Have a basis and write it down. Legitimate interest is usually the workable one for B2B outreach, but it requires you to have actually considered the balance and to be able to show that you did.
• Honour opt-outs properly and permanently. That means across lists and across campaigns, not just within the sequence someone replied to.
• Record where each detail came from. If you cannot say where an address came from, you cannot defend holding it, and you probably should not be using it.
• Set a retention period. A contact you have not used in two years is a liability, not an asset.

None of this makes outreach harder to do well. It mostly rules out the approaches that were not working anyway.

Keep it clean over time

Review {{LIST}} for contact hygiene. Flag anyone we contacted more than {{MAX_TOUCHES}} times with no reply, anyone whose details look stale, and anyone who has gone quiet on their main platform.

Where to run it

Contact enrichment and outreach live in the Favikon app, with Favy able to run the whole flow by prompt. For the same thing inside Claude or ChatGPT, connect the Favikon MCP.