Compelling

Exclude company domains from the workspace's lists. Use this when the user asks to hide companies, such as existing customers or competitors, from lists. Pass domains only. Domains already excluded are reported as skipped. Excluded companies no longer appear in list views. No credits.

compelling_add_to_blacklist

Start a job that finds business contacts by role (names and job titles) at companies in a list. Use this when the user asks for decision-makers or other contacts at companies in a list. roles carries the requested titles or persona as the user stated them, including German titles; account_ids and limit restrict the companies, and per_title_limit caps contacts per company and role. The job runs asynchronously, uses external sources, saves matched contacts to the workspace and the list, and consumes credits (2 per contact found). Returns a run_id and status, plus progress counts if wait_seconds is set. Progress is available from compelling_contacts_run_status; saved contacts from compelling_read_list(record_type='contacts'). It finds names and job titles only: email addresses, phone numbers and LinkedIn profiles are separate insight research. It does not contact anyone. Cost estimates without starting a job come from compelling_estimate_credits(action='find_contacts').

compelling_find_contacts

Start a search that finds new companies matching the user's market and criteria and saves them to a list. Use this when the user asks to build a new list of target companies, for example machinery manufacturers in Germany using SAP, or medtech companies in Austria and Switzerland with ISO 13485 certification. Keep the geography and segment as requested; DACH means Germany, Austria and Switzerland. Required criteria decide membership: a company is added only if it meets all of them. Optional criteria are researched, scored and billed, but do not decide membership. Each criterion becomes a column on the list. The search runs asynchronously, uses external sources and consumes credits. The requested company count is a target, not a guarantee. Progress is available from compelling_find_companies_status; saved companies from compelling_read_list(record_type='accounts'). Companies already stored are found with compelling_search_records. Cost estimates without starting come from compelling_estimate_credits(action='find_companies').

compelling_find_companies

Return a link to the Compelling web app where the user can connect one integration (for example HubSpot, Pipedrive or Google Sheets). Use this when the user asks to connect an app. It does not connect anything itself and does not handle credentials: the signed-in user opens the link in a browser and completes the connection there. Read-only.

compelling_get_integration_link

Return links to the Compelling web app where the user can import a CSV file or sync a list from a connected app. Use this when the user wants to bring data into Compelling from a file or from HubSpot, Pipedrive, Google Sheets or similar. It does not import or upload anything itself: the user opens the link and completes the import in the browser. An app that is not connected yet needs compelling_get_integration_link first. Read-only.

compelling_get_import_link

List the CRM, data and outreach integrations available to the workspace, with connection status and app links. Use this when the user asks which tools are or can be connected. Read-only. Connecting an app requires the user to finish sign-in in the Compelling web app; compelling_get_integration_link returns the link for that.

compelling_list_integrations

List the workspace's lists with id, name and account and contact counts. Use this when the user asks which lists exist or names a list whose id is needed. Sorted by last edit, newest first; supports pagination. Read-only: it does not change lists or records and consumes no credits.

compelling_list_lists

List the workspace's running jobs (company searches, contact searches, research and exports) with their list and run ids. Use this when the user asks what is currently running, or when a run_id or list_id of a running job is needed. Progress of each job is available from its status tool (compelling_find_companies_status, compelling_contacts_run_status, compelling_insight_status). Read-only, no credits.

compelling_list_active_work

List the company domains excluded from the workspace's lists. Use this when the user asks which companies are excluded or hidden. Excluded domains do not appear in list views. Read-only, no credits.

compelling_list_blacklist

List the insight columns of a list: question_id, header and answer type. An insight column is a research question on a list (for example "Uses SAP?" or employee count) whose answers are stored per record. Use this when the user refers to a column by name and its question_id is needed for compelling_run_insight, compelling_read_list (fields, filters, sort_by) or compelling_rank_list. Also lists the system column addedAt, the date a record was added to the list, which compelling_read_list filters accept. Read-only, no credits.

compelling_list_insights

Start scoring a list's companies from 0 to 100 against a weighted rubric of existing columns. Use this when the user asks to prioritize companies in a list by fit or decide which to approach first. The rubric names existing column IDs with weights and point mappings for their values (for example employee count, technology or certification); explain the rubric and weights to the user. A score reflects fit with the rubric, not purchase intent; missing values count as unknown. Runs asynchronously, saves a ranking column and consumes 1 credit per account. Companies only; it does not rank contacts or research missing values. Progress is available from compelling_ranking_status; sorted results from compelling_read_list with sort_by set to the ranking column's question_id. Cost estimates without starting come from compelling_estimate_credits(action='rank_list').

compelling_rank_list

Read the saved companies or contacts of one list, with optional column selection, filters and sorting. Use this when the user wants to view, filter or sort records and their saved insight values (for example Industry or Employees). fields selects columns by header; record IDs and display names are always included. Filters and sorting apply to this response only; sorting by a question_id is available for accounts (column IDs come from compelling_list_insights). Read-only: it does not change the list or its saved filters, does not research missing values, and consumes no credits. Values that were never researched are returned empty.

compelling_read_list

Read the original notes and transcript of one meeting the workspace imported from Granola or Kickscale. Use this when the user needs an exact detail from a meeting (a number, a wording, who said what) that the account timeline does not contain. The content is fetched from the meeting tool at request time and not stored. Only meetings this workspace imported are available. Long transcripts are paged; query returns only matching passages. Read-only, no credits.

compelling_read_meeting

Return the workspace's Company Model as Markdown: the user's own offer, customer and partner segments, and related context. The Company Model describes the user's company: offer, customer and partner segments with buying center, pains, use cases, evidence and competitors (unconfirmed items are marked), recommended ideal-customer searches per segment, recent company searches and the most recently edited lists. Use this when the user asks about their target segments or ideal customer profile, or asks for a new list, search criteria or outreach angle based on their business. Read-only, no credits.

compelling_get_company_model

Start research that fills an existing insight column for selected companies or contacts in a list. Use this when the user asks for new research on records in a list, such as SAP usage, ISO 13485 certification, hiring activity, revenue or employee count for companies, or business email and LinkedIn profile for contacts. The question configured on the column is researched; keep any research period the user requested. Runs asynchronously, uses external sources, consumes credits and saves answers to the list. Rerunning replaces existing answers in that column, including generated message text, so the records, column and any replacement need the user's confirmation first. It does not send messages. Requires account_ids or contact_ids matching record_type, or a limit; question_id comes from compelling_list_insights. Progress is available from compelling_insight_status; saved answers from compelling_read_list. Answers can be inconclusive when no evidence is found. Cost estimates without starting research come from compelling_estimate_credits(action='run_insight').

compelling_run_insight

Search existing companies or business contacts in the workspace by name or domain. Use this when the user wants to find a company or contact already stored in Compelling. Returns record IDs, names, company domains or contact job titles and employers, and list memberships; paginated with limit and offset. Read-only: it searches stored data only, does not discover new companies, does not use external sources, and consumes no credits.

compelling_search_records

Return the workspace's credit spending over a time window and its remaining balance. Use this when the user asks how many credits were spent, on what, or how fast. Returns totals, a breakdown by usage type (company research, contact finding, company search criteria, ranking) and a daily series. Read-only, no credits. Costs of a future action come from compelling_estimate_credits.

compelling_credit_usage

Return the name and domain of the Compelling workspace this connection uses. Use this when the user asks which workspace or company account is connected. The workspace is fixed by the authenticated connection; the result contains no internal identifiers. Read-only, no credits.

compelling_get_workspace

Return a summary of what the workspace knows about one company: saved research, fit with the target profile, missing information and suggested next research. Use this when the user asks what is known about a company, whether it fits their target profile, or what to research next. Identify the company by account id or domain. Suggestions come from fixed rules about missing values; if the company fails the fit check, no further paid research is suggested. Read-only, no credits.

compelling_get_account_knowledge

Sync a list's companies and contacts to a connected CRM (HubSpot, Pipedrive, Attio, Dynamics 365 or monday.com) using the workspace's field mapping. Use this when the user asks to push a list to their CRM. Creates or updates records in the CRM according to the field mapping configured in Compelling. Requires the CRM to be connected and mapped; otherwise it returns an error with a link for the user. Runs in the background, consumes no credits, and returns the sync run id and status.

compelling_sync_list_to_crm

Write companies, contacts and known column values supplied by the user directly into a list. Use this when the user provides data to store in Compelling, such as companies, contacts or values for existing columns. No research and no credits. Existing answers for the supplied question_ids are overwritten, so the records and columns to replace need the user's confirmation first. Columns must exist (compelling_add_insight creates them).

compelling_ingest_records