- Brand
- Connect The Dots
- Category
- Sales & CRM
- Primary Subcategory
- B2B Prospecting & Contact Data
Integration details
Description
Connect The Dots finds warm introductions for sales, recruiting and business development. It maps the professional relationships you and your workspace have shared, and shows the warmest way to reach a person or company. Use it to find and rank warm intro paths, search your network by role, company and location, see how well connected you are to a company, find out who a connector can introduce you to, follow job changes among your contacts, and keep contact notes and people and company lists up to date. You can also draft ghost emails, route them through approvers to the sender, and send them from the sender's mailbox. Workspace admins can manage members and review API usage. Requires an existing Connect The Dots account, and team-wide features need a workspace account. Results are limited to the people and companies your account can access. Notes stay private to their author unless they are shared with the workspace. Connect The Dots does not provide data such as company revenue, funding stage or financial information.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- B2B Prospecting & Contact Data
- Secondary Subcategories
- None listed
- Brand
- Connect The Dots
- Access
- Account required
- First tracked
- 2026-11-14
- Tool count
- 103
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Not discoverable in ChatGPT yet
ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen Connect The Dots suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.
What discovery looks like

Get alerts for Connect The Dots
Get updates when Connect The Dots’s Discoverability Score or category rank changes.
Competing in ChatGPT B2B Prospecting & Contact Data
View Category103 tools agents can invoke
Add recipients to a Ghost Email: more people on "to", or anyone on cc or bcc. Adds several at once. You cannot add the sender here: they are the route tail, changed with update_ghost_email_chain. Someone already a recipient comes back under `already_present` rather than being duplicated. Add recipients BEFORE it is sent. Afterwards the email has already gone out, so a new recipient receives nothing and only makes the reporting counts disagree. With send_type individual_emails (the default) each "to" recipient gets their own separate email and its own outcome, so adding a second one turns a single email into two.
add_ghost_email_recipients
Add a note to a Ghost Email. Two kinds, chosen by `is_private`: • shared (default): a comment visible to you and to everyone the Ghost Email has ALREADY reached, who are notified about it. Use it to give context, answer a question, or explain a change. • private (is_private: true): a note only YOU can ever see. Nobody else on the route sees it and nobody is notified. Use it for your own reminders. The Ghost Email must already have reached you. A note travels BACKWARDS up the route only: anyone still ahead of it will never see this note, not even once it reaches them. So to say something to the NEXT person, do not use this tool. Pass it as the `comment` on forward_ghost_email, which is written at the moment they receive it and is the only note they will see.
add_ghost_email_note
Add a note about a person to your CTD contact notes. Identify the person by human_id: the uuid after /people/ in a person_ctd_url, or in the person's own ctd_url from get_person_details (e.g. https://app.ctd.ai/people/<human_id>; a role's /companies/ link is not a person), or the human_id returned by mark_as_contact or another CTD tool. mark_as_contact returns human_id null when CTD does not know the person yet. Then put the note in mark_as_contact's own note field, or add it here later with a human_id another tool returns once the contact exists. Notes are private by default; set share_with_enterprise to true so everyone in your enterprise workspace can read it. Returns the note_id that update_contact_note and delete_contact_note take. To read the notes a person already has, use list_contact_notes.
create_contact_note
Add one or more companies (by domain) to a company list. Get the list id from list_company_lists. Domains can be sourced from get_company_info or list_reachable_companies.
add_companies_to_list
Add people to the enterprise roster as external members, NOT invited (status to_be_invited), or update the ones already there. Name each person by linkedin_url (preferred), email, or external_member_id; a row matching a stored member updates it and leaves the fields it omits alone. A person added by LinkedIn only gets an email filled in when the enterprise has one. type defaults to other for a new member (see list_external_member_types); relationship_owner must be a user of the enterprise with a connected mailbox. Every row gets its own result, in order, with status succeeded or failed, created true for a new member, and the member. Invite them afterwards with invite_external_members. A coworker (a member of the workspace, or an address in its directory or on its email domains) is never an external member: their row fails with reason_code coworker, and a workspace admin adds them from Members instead. Only an admin of the caller's enterprise can use the external member tools; anyone else gets "User is not an enterprise admin". External members are people outside the company (investors, advisors, board members, partners, customer champions) whose networks the enterprise uses for warm introductions.
add_external_members
Add one or more people (by LinkedIn id) to a people list. Get the list id from list_people_lists. LinkedIn ids can be sourced from tools that return people (e.g. list_reachable_people, get_paths_to_person). Once the new people are scored, the list is re-ranked by score, which replaces any manual card order.
add_people_to_list
Assign one or more existing tags to a single company on a company list. Every tag id must already exist on that list — get them from get_company_list_tags, or create one first with create_company_list_tag. Get the company_id from get_company_list_items. Tags the record already carries come back under already_assigned rather than failing, so this is safe to retry.
add_company_list_item_tags
Assign one or more existing tags to a single person on a people list. Every tag id must already exist on that list — get them from get_people_list_tags, or create one first with create_people_list_tag. Get the human_id from get_people_list_items. Tags the record already carries come back under already_assigned rather than failing, so this is safe to retry.
add_people_list_item_tags
Add people to the workspace by email, giving each a seat. Addresses must be on a workspace domain. Every address gets its own result, in order: added (a new account, provisioned in the background and listed as active within seconds), activated (an existing account on the domain was given the seat; this is also how a deactivated user gets it back, there is no separate activate tool), already_active, or failed with a message. mailbox_sync false adds the person without CTD ever reading their mailbox. Confirm the list with the user before calling: a seat is billable. Only an admin of the caller's workspace can use the user management tools; anyone else gets "User is not an enterprise admin". Team Edition workspaces are not supported. Users are the people with a CTD seat in the workspace, as the admin console's User Management page shows them; external members are a separate roster with their own tools.
add_workspace_users
Update the pipeline stage and/or manual note for many companies in a single call (1-500 companies). Each update identifies its company by EITHER company_domain OR company_linkedin_url (exactly one) — get these from get_company_info or list_reachable_companies — and must set company_stage, manual_note, or both. Updates may be applied immediately or queued for asynchronous processing; queued changes appear within a few hours. The result reports per-company success/deferred/error so partial failures are visible. Requires a Business plan.
bulk_update_company_stage
Move a company to a different kanban status (column) in a company list, and optionally set its position within that column. Get the list id from list_company_lists and valid status ids from get_company_list_statuses. Pass status_id: null to clear the company's status.
change_company_list_item_status
Move a person to a different kanban status (column) in a people list, and optionally set their position within that column. Get the list id from list_people_lists and valid status ids from get_people_list_statuses. Pass status_id: null to clear the person's status.
change_people_list_item_status
Create a Ghost Email: an email that someone else sends, on your behalf, to a recipient. You author it and plan its whole route up front; you never send it yourself. `participants` is who RECEIVES it (to / cc / bcc); `route` is who HANDLES it on the way, ending with the sender. The sender goes in `route`, never in `participants`, and you never add a "from". NOTHING IS SENT OR SHARED. It is created and sits with you; forward_ghost_email hands it on. Someone who is not a CTD user can sit anywhere on the route, sender included: identify them by email and they are invited when it reaches them. Use human_id alone ONLY for an existing CTD user, otherwise send their email too or the forward fails later. APPROVERS. An enterprise can require approval for a connector, or set a default for everyone. If the caller belongs to one, call get_approvers_for_connector first and put whoever it names into `route` ahead of the sender: routing through them IS the approval. Nothing blocks you if you cannot, so say so rather than skipping them silently. CHANNELS. `channel` is how the sender delivers it: `email` (default, sent from their mailbox), `linkedin` (they paste it into a LinkedIn message) or `phone` (they text it). On linkedin / phone there is exactly ONE "to" and no cc/bcc, the body is plain text (no HTML, no subject needed), and nothing is sent by CTD: the sender copies the text, sends it themselves and records it with mark_ghost_email_sent. Give the recipient a `linkedin_url` or `phone_number` when you have one; otherwise CTD fills it from the author's and the sender's contacts, and the sender is asked for it if nobody has it.
create_ghost_email
Create a new static company list owned by the caller, optionally pre-populated with companies by domain. Use when the user wants a brand-new company list (e.g. "make a list of my target accounts"). Each domain is resolved to a company (created if unknown) and added; the response returns the new list and the companies added. Domains are optional — omit them to create an empty list and add later. Does NOT add to an existing list (use add_companies_to_list) and does NOT create a people list (use create_people_list).
create_company_list
Create a tag on a company list. Tags label individual records on the list (e.g. "Warm intro", "Follow up") and are the same tags shown in the CTD web app. Tag names are unique per list. Once created, assign the tag to records with add_company_list_item_tags. Use get_company_list_tags first to check whether a suitable tag already exists.
create_company_list_tag
Create a new static people list owned by the caller, optionally pre-populated with people by email and/or LinkedIn URL. Use when the user wants a brand-new people list (e.g. "make a list of these prospects"). Emails and LinkedIn URLs are each resolved to known people and added; the response returns the new list, the people added, the LinkedIn URLs queued for enrichment (`pending`), and emails that matched no one (`unresolved_emails`). Both arrays are optional — omit them to create an empty list and add later. Does NOT add to an existing list (use add_people_to_list) and does NOT create a company list (use create_company_list).
create_people_list
Create a tag on a people list. Tags label individual records on the list (e.g. "Warm intro", "Follow up") and are the same tags shown in the CTD web app. Tag names are unique per list. Once created, assign the tag to records with add_people_list_item_tags. Use get_people_list_tags first to check whether a suitable tag already exists.
create_people_list_tag
Create an external member type. Its slug is derived from the name ("Limited Partner" becomes limited_partner) and cannot change later; a name that would repeat an existing slug is refused. Only an admin of the caller's enterprise can use the external member tools; anyone else gets "User is not an enterprise admin". External members are people outside the company (investors, advisors, board members, partners, customer champions) whose networks the enterprise uses for warm introductions.
create_external_member_type
Deactivate a workspace user: their seat is removed and CTD stops reading their mailboxes; their data is kept and the workspace keeps what their network contributed so far. Only an active user can be deactivated, and the calling admin cannot deactivate themselves. Repeating the call on a deactivated user changes nothing. To give the seat back, add_workspace_users with the same address. Confirm with the user first. Only an admin of the caller's workspace can use the user management tools; anyone else gets "User is not an enterprise admin". Team Edition workspaces are not supported. Users are the people with a CTD seat in the workspace, as the admin console's User Management page shows them; external members are a separate roster with their own tools.
deactivate_workspace_user
Decline a Ghost Email: refuse to pass it on. HOLDER-ONLY: only whoever is currently holding it may decline. This ENDS the Ghost Email permanently. Nobody further down the route ever receives it, everyone who handled it earlier is notified, and it cannot be reopened or re-sent. Always confirm with the user first. Decline means "I will not do this". If the user simply does not want the Ghost Email any more, delete_ghost_email is the right tool: it removes it quietly instead of telling everyone it was refused. Give a `reason`: it is what the author sees, and it is the only explanation they get.
decline_ghost_email
Permanently delete a Ghost Email, along with its route and recipients. CREATOR-ONLY: only the person who created it can delete it. This cannot be undone, so confirm with the user first. Use this for "never mind, scrap it". To refuse a Ghost Email someone handed to YOU, use decline_ghost_email instead: that tells the author it was refused, which deleting does not.
delete_ghost_email
Permanently delete a company list. This removes the list and its kanban configuration; it does not delete the companies themselves from CTD. Get the list id from list_company_lists. This action cannot be undone, so confirm with the user first.
delete_company_list
Delete a tag from a company list entirely. This removes the tag from every record on the list that carried it, and cannot be undone, so confirm with the user first. To untag a single company while keeping the tag available, use remove_company_list_item_tag instead. Get the tag id from get_company_list_tags.
delete_company_list_tag
Permanently delete one of your own contact notes. Get note_id from list_contact_notes, where only notes with created_by_me true can be deleted, or from create_contact_note. This cannot be undone, so confirm with the user first. To keep the note but hide it from your enterprise, use update_contact_note with share_with_enterprise false instead.
delete_contact_note
Delete a tag from a people list entirely. This removes the tag from every record on the list that carried it, and cannot be undone, so confirm with the user first. To untag a single person while keeping the tag available, use remove_people_list_item_tag instead. Get the tag id from get_people_list_tags.
delete_people_list_tag
Delete an external member, whatever their status. An accepted member leaves the enterprise first, so their network stops feeding its paths; their own CTD account is untouched. The member's uploaded LinkedIn connections go with them. Cannot be undone: confirm with the user first. Only an admin of the caller's enterprise can use the external member tools; anyone else gets "User is not an enterprise admin". External members are people outside the company (investors, advisors, board members, partners, customer champions) whose networks the enterprise uses for warm introductions.
delete_external_member
Delete an external member type. Members of that type move to other. Default types cannot be deleted. Confirm with the user first. Only an admin of the caller's enterprise can use the external member tools; anyone else gets "User is not an enterprise admin". External members are people outside the company (investors, advisors, board members, partners, customer champions) whose networks the enterprise uses for warm introductions.
delete_external_member_type
Edit a Ghost Email that has not been sent yet. Send only the fields you are changing; at least one is required. METADATA is the exception: the author can change it at any time, also after it is sent (e.g. to record an outcome), and only the author can. If the body still contains {{ variable }} placeholders, resolve them with this tool before anyone sends it. RECIPIENT vs TARGET are separate and change independently. `recipient` replaces who RECEIVES the email; `target_human_id` changes who the ask is ABOUT (they differ for an introduction, where you email a connector about a third person). LIMIT: `recipient` rewrites ONE "to" recipient, and with several of them WHICH one is undefined: there is no notion of a primary "to". Use it only when there is exactly one recipient. Recipients cannot be added or removed, and cc/bcc cannot be changed at all; if those are wrong, delete the Ghost Email and create a new one. To change the ROUTE (who handles it) use update_ghost_email_chain, not this tool. CHANNEL. `channel` switches how the sender delivers it (email, linkedin, phone); anyone on a live route may. Moving to linkedin / phone needs exactly one "to", no cc/bcc and no attachments, and turns the body into plain text. Give the recipient a `linkedin_url` / `phone_number` through `recipient` when you have one.
update_ghost_email
Edit one of your own contact notes: replace its text, change who can see it, or both (at least one). Get note_id from list_contact_notes, where only notes with created_by_me true can be changed, or from create_contact_note. note_text replaces the whole note rather than appending to it. share_with_enterprise true shares the note with everyone in your enterprise workspace, false makes it private again; leave it out to keep the current sharing.
update_contact_note
Find ranked warm introduction paths to a company or person, returned as one unified set of paths shared by everyone in the caller's enterprise/workspace (the team-wide view — see the note below), rather than from the calling user's personal perspective. Returns up to 20 paths sorted strongest first, each with the chain of people, relationship strengths, and a `why_recommended` explanation. Provide exactly one of: company_domain, company_linkedin_url, person_email, person_linkedin_url. Business plan only. Use get_paths_to_company / get_paths_to_person for the caller's personal-perspective variant. "Global" here does NOT mean more data or access to other enterprises' graphs — it reaches the SAME network as the non-global tools. The only difference is whose perspective the paths are computed from: the regular tools return paths from the CALLING user's own perspective, while the global tools return one unified set of paths shared by EVERYONE in the caller's enterprise/workspace. Example: asked for paths to Google, the regular tool shows you 'you → Drew (your coworker) → CEO' (a 2nd-degree path from your perspective) while Drew sees his own direct 'Drew → CEO'; the global tool shows BOTH of you the same canonical 'Drew → CEO of Google'. Use it so teammates see consistent, identical results — not to reach a wider network. Each hop may include `relationship_via_company_domain`: more detailed context on how you or a co-worker know the next person (email and meeting counts and dates), counted only from company email and calendar accounts; personal accounts such as Gmail are never included. It appears only when the enterprise admin has enabled it. `null` means it is not available to you; `{"email": null, "calendar_summary": null}` means no recorded interactions through company accounts. Note on `stage`: each returned path's top-level `stage` is the target person's WINNING stage — a single representative stage chosen across ALL of that person's current roles (it favors the more advanced/positive stage). It can therefore differ from a stage you filtered on. The actual per-role stages (including the one that matched your filter) are listed in `target_current_roles[].path_stage`. This is expected behavior, not a filter error.
list_global_paths
List paths filtered by pipeline stage (e.g. "To do", "Approaching Connector", "Approaching Target"). Returns up to 20 paths sorted strongest first, each with `path_id` and `stage` so you can follow up with update_path_stage. Filterable only by pipeline stage (this endpoint accepts no other filters — for degree/seniority/function/location filtering use search_paths or get_people_in_company). Requires a Business plan. Note on `stage`: each returned path's top-level `stage` is the target person's WINNING stage — a single representative stage chosen across ALL of that person's current roles (it favors the more advanced/positive stage). It can therefore differ from a stage you filtered on. The actual per-role stages (including the one that matched your filter) are listed in `target_current_roles[].path_stage`. This is expected behavior, not a filter error.
get_paths_by_stage
Find all paths that flow through a specific connector (a person in your network who can make warm introductions). Returns up to 20 paths sorted strongest first, each with `path_id` and `stage`. Identify the connector by either their email or LinkedIn URL. Filterable by connection degree, relationship strength, target persona, title, seniority, function, location, connector type, and path attributes. Useful when you want to know who a specific contact can connect you to. **For queries like "who does X know at Y company", prefer search_paths first** ("senior people {connector} knows at {company}") — it can surface direct connections this structured endpoint misses. Fall back to this tool with `company_domain` set when search_paths returns 0 or noisy results. Requires a Business plan. Each hop may include `relationship_via_company_domain`: more detailed context on how you or a co-worker know the next person (email and meeting counts and dates), counted only from company email and calendar accounts; personal accounts such as Gmail are never included. It appears only when the enterprise admin has enabled it. `null` means it is not available to you; `{"email": null, "calendar_summary": null}` means no recorded interactions through company accounts. Note on `stage`: each returned path's top-level `stage` is the target person's WINNING stage — a single representative stage chosen across ALL of that person's current roles (it favors the more advanced/positive stage). It can therefore differ from a stage you filtered on. The actual per-role stages (including the one that matched your filter) are listed in `target_current_roles[].path_stage`. This is expected behavior, not a filter error.
get_paths_by_connector
Find all paths that flow through a specific connector, returned as one unified set of paths shared by everyone in the caller's enterprise/workspace (the team-wide view — see the note below), rather than from the calling user's personal perspective. Returns up to 20 paths sorted strongest first. Identify the connector by either their email or LinkedIn URL. Business plan only. Use get_paths_by_connector for the caller's personal-perspective variant. "Global" here does NOT mean more data or access to other enterprises' graphs — it reaches the SAME network as the non-global tools. The only difference is whose perspective the paths are computed from: the regular tools return paths from the CALLING user's own perspective, while the global tools return one unified set of paths shared by EVERYONE in the caller's enterprise/workspace. Example: asked for paths to Google, the regular tool shows you 'you → Drew (your coworker) → CEO' (a 2nd-degree path from your perspective) while Drew sees his own direct 'Drew → CEO'; the global tool shows BOTH of you the same canonical 'Drew → CEO of Google'. Use it so teammates see consistent, identical results — not to reach a wider network. Each hop may include `relationship_via_company_domain`: more detailed context on how you or a co-worker know the next person (email and meeting counts and dates), counted only from company email and calendar accounts; personal accounts such as Gmail are never included. It appears only when the enterprise admin has enabled it. `null` means it is not available to you; `{"email": null, "calendar_summary": null}` means no recorded interactions through company accounts. Note on `stage`: each returned path's top-level `stage` is the target person's WINNING stage — a single representative stage chosen across ALL of that person's current roles (it favors the more advanced/positive stage). It can therefore differ from a stage you filtered on. The actual per-role stages (including the one that matched your filter) are listed in `target_current_roles[].path_stage`. This is expected behavior, not a filter error.
list_global_paths_by_connector
Find ranked warm introduction paths to anyone at a specific company. Returns up to 20 paths sorted strongest first, each with the chain of people (you -> connector(s) -> target), their titles, relationship strengths, `path_id`/`stage` (for pipeline management via update_path_stage), and a `why_recommended` explanation. Requires either company_domain (e.g. "stripe.com") or company_linkedin_url. Filterable by connection degree, relationship strength, target persona, title, seniority, function, location, connector type (e.g. connector_type: ["co-worker"] for paths through teammates), and path attributes. Use the domain or LinkedIn URL returned by list_reachable_companies. Each hop may include `relationship_via_company_domain`: more detailed context on how you or a co-worker know the next person (email and meeting counts and dates), counted only from company email and calendar accounts; personal accounts such as Gmail are never included. It appears only when the enterprise admin has enabled it. `null` means it is not available to you; `{"email": null, "calendar_summary": null}` means no recorded interactions through company accounts. Note on `stage`: each returned path's top-level `stage` is the target person's WINNING stage — a single representative stage chosen across ALL of that person's current roles (it favors the more advanced/positive stage). It can therefore differ from a stage you filtered on. The actual per-role stages (including the one that matched your filter) are listed in `target_current_roles[].path_stage`. This is expected behavior, not a filter error.
get_paths_to_company
Get relationship paths to a specific contact in the caller's personal CTD graph, looked up by LinkedIn URL. Distinct from get_paths_to_person (which uses the enterprise-wide graph): this tool surfaces the connections visible from the caller's own contact data.
get_paths_to_contact
Find ranked warm introduction paths to a specific person. Returns up to 20 paths sorted strongest first, each with the chain of people (you -> connector(s) -> target), their titles, relationship strengths, `path_id`/`stage` (for pipeline management), and a `why_recommended` explanation. Requires either person_email or person_linkedin_url (an exact identifier - not a name). If you only have a name, ask the user for the email or LinkedIn URL first. Filterable by connection degree, relationship strength, connector type (e.g. connector_type: ["co-worker"] for paths through teammates), and target attributes. Each hop may include `relationship_via_company_domain`: more detailed context on how you or a co-worker know the next person (email and meeting counts and dates), counted only from company email and calendar accounts; personal accounts such as Gmail are never included. It appears only when the enterprise admin has enabled it. `null` means it is not available to you; `{"email": null, "calendar_summary": null}` means no recorded interactions through company accounts. Note on `stage`: each returned path's top-level `stage` is the target person's WINNING stage — a single representative stage chosen across ALL of that person's current roles (it favors the more advanced/positive stage). It can therefore differ from a stage you filtered on. The actual per-role stages (including the one that matched your filter) are listed in `target_current_roles[].path_stage`. This is expected behavior, not a filter error.
get_paths_to_person
Hand a Ghost Email to the next person on its route. This is how a Ghost Email moves: the author forwards it to the first approver (or straight to the sender), each approver forwards it onward, and the last person sends it with send_ghost_email. HOLDER-ONLY: only the person currently holding the Ghost Email can forward it. Use get_ghost_email to check: `is_your_turn` tells you whether you may, and `waiting_on` names whoever may instead. By default it goes to the next person already planned on the route. Supply `next` only to change course: that person REPLACES the next planned hop, or is appended when no one is planned after you. Everyone further down the planned route is kept. Forwarding is what invites people: someone identified only by email, who is not yet a CTD user, gets invited at this moment. A person identified by human_id who turns out not to be a CTD user, and has no email on the route, fails here. Re-plan that hop with update_ghost_email_chain, giving their email. Use `comment` to tell the recipient why it is coming to them. They see it (it is written once the Ghost Email has reached them), and so does everyone who has already handled it. Anyone still ahead on the route never sees it, not even once it reaches them, so a note cannot be left for a later hop. Before calling, tell the user who it goes to next, and wait for them to confirm.
forward_ghost_email
Read one Ghost Email in full: subject, body, recipients, the route with each person's state, and the comments on it. Call this before forwarding, sending, editing or declining: it is what tells you whether you may: `is_your_turn` (you may forward or decline), `can_send` (you are last on the route and may send), and `waiting_on` (who may act if you may not). You must be on the route to read it. `channel` says how the sender delivers it: email (send_ghost_email), or linkedin / phone, where the recipient carries a `linkedin_url` / `phone_number`, the body is plain text, and the sender copies it, sends it by hand and records it with mark_ghost_email_sent (`sent_note` keeps what they said). If `route_truncated` is true you are the sender and are seeing only the person who handed it to you, not the whole route, so say so rather than describing it as the full journey.
get_ghost_email
Get a single company list by its id, including its metadata and (paginated) member companies. Get the list id from list_company_lists.
get_company_list
Get a single people list by its id, including its metadata and (paginated) member people. Get the list id from list_people_lists.
get_people_list
List the company items in a company list, optionally filtered by kanban status. Get the list id from list_company_lists and the available status ids from get_company_list_statuses.
get_company_list_items
List the kanban statuses (columns) defined on a company list. Returns each status with its id and name. Use these status ids to filter get_company_list_items or to move a company with change_company_list_item_status.
get_company_list_statuses
List the tags defined on a company list, each with its id, name and color. Use these tag ids to assign tags with add_company_list_item_tags, or to see which tags already exist before creating a new one with create_company_list_tag. To see which tags each record currently carries, use get_company_list_items.
get_company_list_tags
Find who your enterprise expects to approve a Ghost Email sent through a particular connector. An enterprise can set approvers per connector or a default approver for everyone, so call this before create_ghost_email whenever the caller belongs to one. Approval happens through the route: put the people this names into `route`, in order, in front of the connector who will send. The Ghost Email then travels through them on its way to the sender, and each one forwards it on, or declines. Each approver comes back with a connected_ctd_user_id and a human_id: pass either straight into a route entry. If the response marks approval mandatory, route through them; if for some reason you cannot, say so rather than refusing to create the Ghost Email. Requires a Business plan.
get_approvers_for_connector
Get one external member, named by exactly one of external_member_id, email or linkedin_url. Also the way to check "do we already have this person" before add_external_members. Besides the list fields it returns about (who they are to us, visible to the whole company), ask_budget, ask_activity (how often they were asked: open now, in the last 30 / 90 / 180 days, all time, sent, declined, last asked, remaining_in_period) and signature. Not found is a normal answer, not an error to retry. A LinkedIn profile shared by several members returns their ids; pick one by id. Only an admin of the caller's enterprise can use the external member tools; anyone else gets "User is not an enterprise admin". External members are people outside the company (investors, advisors, board members, partners, customer champions) whose networks the enterprise uses for warm introductions.
get_external_member
Get extended details about a company in the caller's graph, looked up by domain OR LinkedIn URL. Returns firmographics (industry, headcount, etc.) plus CTD network data about the caller's reach into the company: • number_of_contacts — how many people at the company the caller is directly connected to; • number_of_potential_contacts — how many people at the company the caller can reach through their network; • ctd_company_score_scaled — CTD company score, an integer from 1 to 3 reflecting how strong the caller's relationships into the company are (null when there are no scored contacts); • ctd_company_score_label — that score as a label: "weak", "medium", or "strong" (null/"very weak" when there is no data). Use this when the user wants more than the basic firmographics returned by get_company_info — e.g. "tell me more about Stripe."
get_company_details
Get everyone you and one specific other person (the "connector") both know — your mutual contacts with them. Look the connector up by LinkedIn URL (preferred) OR email; they do NOT have to be a CTD user. Returns the `connector` you asked about, then `mutual_contacts`: for each shared contact their name, `emails` (most recently communicated with first), `title`, `company_name`, `location`, and CTD links. Crucially, each one carries TWO relationships: `relationship_with_user` (how YOU know them) and `relationship_with_connector` (how the CONNECTOR knows them) — each with `relationship_type` (e.g. "email connected" / "linkedin connected" / "overlapped"), `relationship_strength` 1-3 and `relationship_strength_label`. Use this to answer "who do we both know?", "who can vouch for me with X?", or to pick the strongest shared contact to ask for an introduction to the connector. This is NOT path discovery to a stranger — for that use get_paths_to_person. Use this when you already know WHO the person is and want the overlap between your network and theirs.
get_mutual_contacts
List the people items in a people list, optionally filtered by kanban status. Get the list id from list_people_lists and the available status ids from get_people_list_statuses.
get_people_list_items
List the kanban statuses (columns) defined on a people list. Returns each status with its id and name. Use these status ids to filter get_people_list_items or to move a person with change_people_list_item_status.
get_people_list_statuses
List the tags defined on a people list, each with its id, name and color. Use these tag ids to assign tags with add_people_list_item_tags, or to see which tags already exist before creating a new one with create_people_list_tag. To see which tags each record currently carries, use get_people_list_items.
get_people_list_tags
Connect The Dots ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Connect The Dots's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Connect The Dots alternatives on ChatGPT?
As of 2026-11-15, Connect The Dots competes with Add to CRM, AdvPulse, AgentData, AgentSource, AI Leads Scout, AI Vibe Prospecting, anVendor, Apollo.io and 85 more in ChatGPT B2B Prospecting & Contact Data, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.


