Prompt Prospect
Prompt Prospect v1.2.1
Find conference attendees
From the developer
Declared capabilities
- Read
- Write
Cost & access
This plugin does not sell products or process payments. It finds conferences and the people and companies at them, and saves notes and statuses in the user's Prompt Prospect workspace.
Declared limitations
- Travel and ticketing for a conference. Prompt Prospect does not sell tickets, book travel or take payments.
- Private contact details. Prompt Prospect never holds personal email addresses or phone numbers.
- Personal gatherings that are not professional events. Prompt Prospect only covers conferences, expos and trade shows.
Onboarding example
Who is speaking at Money20/20 USA, and which speakers work at banks?
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 16, 2026.
Description
From the marketplace listing
Prompt Prospect is a sales prospecting tool for conferences, expos and trade shows. It gives you the attendee list for any event: who is speaking, exhibiting, sponsoring and attending, so your sales or business development team knows who to meet before you go. Search a curated catalog of upcoming conferences by city or industry (fintech, SaaS, healthtech, HR tech, martech, security and more), or add any event by its website. Prompt Prospect researches the event's own pages and its LinkedIn activity and builds the event attendee list: the speaker list, the exhibitor list, sponsors, organizers and the people engaging with the event online, each with their company and the source that puts them there. Set your target customer once in Prompt Prospect and every attendee and company is checked against it automatically, so the best leads rise to the top. Then ask who to meet: "Who is speaking at Money20/20 and works at a bank?", "Which exhibitors at HLTH sell to hospitals?", "Which sponsors at Web Summit match my target customer?" Trace a company or a speaker across events: "What other conferences is U.S. Bank sponsoring or exhibiting at?" Save the people worth meeting, keep notes, record meetings and outcomes; the full list exports from the Prompt Prospect app for outreach. Use it for conference prospecting and trade show lead generation: find who is attending an event, build a speaker or exhibitor list, research sponsors before an expo, and plan meetings at summits and industry events. Prompt Prospect returns names, roles, companies and public profile links with their evidence. It never returns personal email addresses or phone numbers.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 16, 2026. Last seen Nov 17, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
EventHex helps event organizers list and configure franchise events, manage tickets and agendas, review registrations and analytics, and ...
Shared terms: attendee, organizer, event, website
-
Find professionals by describing them in plain English, open their LinkedIn profiles and get their verified work emails.
Shared terms: find, companie, industry, lead
-
Find warm introductions and manage target companies through your team's professional network.
Shared terms: find, companie, know, target
-
Find B2B leads, company data and verified work emails with Deeplead.
Shared terms: find, companie, industry, lead
-
Find leads, enrich contacts, run multi-channel outreach sequences, and manage your sales pipeline — from any AI assistant.
Shared terms: find, companie, lead, prospect
Keywords
Files & skills
File archives
Skill instructions
find-people-at-an-event2.91 KB
--- name: find-people-at-an-event description: Show who is going to a researched conference and why, filtered by role, company, fit or relationship (speaker, sponsor, exhibitor, engaged attendee). Use when the user asks who will be at an event, who there matches their target customer, wants a list of people or companies from it, or asks why someone is on the list. --- Work from evidence the workspace already holds. Nothing here spends anything. 1. **Resolve the event.** Call `list_my_events` and match the user's words to a saved event. If it is not saved, hand over to the `plan-a-conference` skill. If research has not finished (`event_overview` shows `research.status` other than complete or partial), say what has been found so far and when to check back. 2. **Filter, do not dump.** Call `list_event_people` with the narrowest useful filters: `q` for a role, company or name; `relationship` for speakers, sponsors, exhibitors or engaged attendees; `category` for sponsor, exhibitor or speaker companies; `fit` for STRONG and PLAUSIBLE when the user wants the people who match their target customer; `edition` for a past year. Default `limit` is 40; page with `offset` only when the user asks for more. 3. **No target customer yet?** When the answer carries a `note` saying no target customer is set, nobody has a fit verdict: tell the user that in one line, give the settings link from the note (the target customer is set in the Prompt Prospect app, not here), and answer with the unfiltered list instead. Do not guess who matches. 4. **Present people with their evidence.** For each person give name, headline, company and the one-line reason they are on the list (the evidence excerpt and source); when they were checked, add their fit and the reason. Group by relationship when the list mixes them. Companies come from `list_event_companies` with their role, fit and how many of their people are in the event. 5. **Go deeper on request.** `get_person` returns one person's profile, every observation and the other conferences they are listed at; use it when the user asks "why is this person here", doubts an entry, or asks where else they speak. `search_prospects` searches across every saved event when the user asks about a person or company rather than one event. 6. **Save decisions.** When the user says they want to meet someone, call `set_people_status` with `pursue` (or `watch` for later, `dismiss` to drop), passing the people's `link_id` values from `list_event_people` as `link_ids`. Notes, meetings and outcomes are the `keep-track-of-people` skill. Boundaries: attendance is only ever what the evidence shows; say "listed as a speaker" or "engaged with the event's posts", never "will attend". A fit verdict is Prompt Prospect's judgment against the saved target customer, so present it as "judged a strong fit", not as fact about the person. Do not fabricate contact details; the tools return LinkedIn profile URLs, not emails or phone numbers.
keep-track-of-people2.06 KB
--- name: keep-track-of-people description: Keep the workspace's record of a person at an event up to date: save or dismiss them, replace the note, record a meeting on the event calendar, mark outcomes (contacted, replied, meeting booked or held, opportunity). Use when the user says they want to meet, met, contacted or heard back from someone, or wants a note kept. --- Two tools write, both scoped to one saved event, and nothing here contacts anyone. 1. **Identify the person.** Take the `link_id` from `list_event_people`, `get_person` or `search_prospects` (the `events` entries carry it). Pass it as `event_person_id` to `update_person`, or in `link_ids` to `set_people_status`. If the user names someone you have not listed yet, find them first; never guess an id. 2. **Status.** `set_people_status` with `pursue` (going after them), `watch` (later), `dismiss` or `new` (undo) takes several people at once. `update_person` takes `status` too, for one person along with other changes. 3. **Notes.** `update_person` with `note` replaces the whole note, so read the current note from `get_person` (`profile.note`) and carry forward what the user wants kept. Write the note in the user's words; do not add claims they did not make. An empty string clears it. 4. **Meetings.** `update_person` with `meeting_at` (an ISO 8601 time with offset), `meeting_where` and `meeting_about` records the meeting on the event's own calendar in Prompt Prospect. Resolve day names against the event's dates from `event_overview` and ask when the time is ambiguous. This sends no invitation and confirms nothing with the other person: say "recorded", never "booked" or "scheduled with". `meeting_at: null` clears it. 5. **Outcomes.** `update_person` with `outcomes` marks what happened (`contacted`, `replied`, `meeting_booked`, `meeting_held`, `opportunity`); `clear_outcomes` undoes one. Mark only what the user reports. Boundaries: only the fields the user asked about change (the tool leaves the rest alone); confirm the person's name back in the answer; never record a meeting or an outcome the user did not state.
plan-a-conference1.98 KB
--- name: plan-a-conference description: Find the right conferences for someone, save one to their Prompt Prospect workspace and start its research. Use when the user asks which events to attend, wants a conference near a place or in an industry, or names an event to add. --- Use the Prompt Prospect tools in this order. Every tool answers with plain data; report it in the user's terms. 1. **Find candidates.** Call `find_events` with what the user gave: `near` (a US city or metro), `category` (fintech, saas, martech, hrtech, healthtech, security, and so on) or `q` (a keyword). Ask for a place or a topic only if the user gave neither. Show up to five results with date, city and organizer, and say which are already in the workspace (`in_workspace_event_id` is set). 2. **Confirm before adding.** `add_event` saves the event and starts research, which reads the event's pages and posts. Research is included, but it runs for 5 to 20 minutes and it is the user's workspace, so name the event and ask once before calling it. Pass `catalog_slug` for a catalog event or `url` for any other event website. If the answer carries `code: "event_limit_reached"`, the workspace has used the events its plan includes: say so, with the limit and when the count starts over (both are in the answer); do not retry. 3. **Tell them what happens next.** Research runs on Prompt Prospect's side. The user is emailed when it finishes, and `event_overview` shows progress (`research.status`, people found so far) whenever they ask. Do not poll on your own. Once research finishes, Prompt Prospect checks everyone against the workspace's target customer by itself; `event_overview`'s `next_step` says when that is still pending. 4. **Already researched?** If `list_my_events` or `find_events` shows the event with people found, skip to the `find-people-at-an-event` skill instead of adding it again. Boundaries: never invent an event, date or venue; if `find_events` returns nothing, say so and offer to add the event by its website URL.
trace-across-events1.91 KB
---
name: trace-across-events
description: Find the other conferences a company, speaker, exhibitor or sponsor is listed at, across Prompt Prospect's catalog and the user's workspace. Use when the user asks where else a company exhibits or sponsors, which events a person speaks at, or whether a prospect will be at another event.
---
The cross-event answer comes from two tools; both read Prompt Prospect's own index and spend nothing.
1. **A company.** Call `get_company` with `name` (or `domain` when the user gives a website). Starting from an event, pass `event_id` and the company's `company_id` from `list_event_companies` instead, which also returns its role, fit and people at that event. The answer's `other_events` lists each edition with the year, dates, place, the role the source gives (exhibitor, sponsor, partner, speaker company, attendee company) and `in_workspace_event_id` when the user already has it saved. `found: false` means the index has no such company; say so rather than guessing.
2. **A person.** Call `get_person` with `event_id` and the person's `link_id` (from `list_event_people`) as `event_person_id`. Its `other_events` lists the conferences the same person is listed at, with their role at each and `employers` as the sources recorded them. A person cannot be looked up by name alone: find them at an event first, or use `search_prospects` across the user's events.
3. **Present it as a timeline.** Sort by date, say the role at each event ("exhibiting at HLTH 2026, sponsored Money20/20 2025"), and note `year_estimated` when a year was inferred. Offer `plan-a-conference` for an event the user does not have yet (`catalog_slug` is given when the event is in the catalog).
Boundaries: a listing is a listing; say "listed as an exhibitor", not "will be there". Engaging with an event's posts is not counted as going, and the tools say so in `other_events_note`. Never pad the list with events the tools did not return.
Release notes
Prompt Prospect for ChatGPT, 1.2.1. Find conferences, expos and trade shows by city or industry. See who is speaking, exhibiting, sponsoring and attending, with the evidence that puts each person there, and who matches your target customer. Trace a company or speaker across events. Save the people worth meeting, keep notes, and record meetings and outcomes.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package license
- MIT
- Package author
- Prompt Prospect
- Keywords
- See keywords
- Commerce declaration
- Does not support commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Read
- Write
Package observed Nov 16, 2026.
Technical details
- First seen
- Nov 16, 2026 · 18:00 UTC
- Last seen
- Nov 17, 2026 · 12:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ac282cedb2c819190cba85299804ac8
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.