Connect Your AI Agent with Super Carl for Slack

Create a Super Carl outbound communication and optionally send it through Gmail, LinkedIn, X, Instagram, or Super Carl channels. Dry Run defaults to true; set it to false only after Check Communication Capabilities passes and the user approves live delivery. See the documentation

Search Super Carl post and activity signals, including authored posts, comments, likes, reactions, company mentions, and engagement. Use this before Search People when the workflow is anchored on someone posting or engaging with content; enable With People to return deduped actors from matching activity. Post rows can be large — pass Fields (flat field names only, e.g. author_name, text, url; there is no nested author.name path) to keep the result small; With People's deduped rows are already trimmed and don't need Fields. See the documentation

Search people by role, company history, expertise, location, network relationship, or recent activity. Keep Preview enabled for fast counts and lightweight rows; disable Preview when you need full rows and Evidence Format, since Evidence Format is ignored during preview. Use Search Companies first when a named employer is ambiguous. Person rows carry deep connection/evidence metadata and can be large — pass Fields (e.g. name, linkedin_profile_url, headline) to keep the result small when you only need a few values. Always pass Fields when Preview is off and you set Relationship Detail to intro_paths or Evidence Format to anything other than none: that combination alone can exceed the response size limit even with a handful of rows, so don't wait for a truncated first call to add Fields. Read-only against Super Carl's shared external people database: there is no way to edit, hide, or delete a person's profile through this or any other Super Carl tool. See the documentation

Search jobs when the workflow needs hiring-company opportunities, role fit, or warm paths into employers. Use Search People for candidate/advisor discovery, and enable With People when the workflow should return 1st/2nd-degree contacts at each hiring company. filters.locations scopes the hiring company/people, not the job posting itself — check applied_filter_summary.people_company_scope in the response to see how a location filter was actually applied, and don't retry the same query with reworded locations if it comes back applied_as_job_posting_filters: false, since that's a scope limitation, not a bad query. Job rows can be large — pass Fields (flat field names only, e.g. title, company_name, location, primary_source_url; there is no nested company.name path) to keep the result small. See the documentation

Search companies by name, domain, funding, size, industry, location, growth, or technology. Use this to qualify a target company or find companies matching structured Filters before reaching out. Use Search People afterward to find people at a matched company; enable Resolve Only to just disambiguate a single company name, domain, or LinkedIn URL without running a full search — Resolve Only returns identity metadata ONLY (name, domain, a coarse employee_count, industries), never a company's real size or description. When the task needs to know a company's actual size or what it does, leave Resolve Only off (or set it false) and set Result Mode to detailed; don't fill gaps from outside knowledge when Resolve Only comes back thin — re-call with detailed instead. Company rows in detailed mode can be large — pass Fields (e.g. name, domain, employee_count) to keep the result small. See the documentation

Check Super Carl network readiness before running Search People, Search Jobs, or Search Companies. Use this to inspect LinkedIn/Gmail/Super Carl graph sync status for the API key owner or a delegated team-seat user via Delegate User ID; low or unsynced counts can explain weak network-aware results. See the documentation

Fetch a Super Carl communication record, normalized status, recent events, task metadata, and artifact URLs after Send Communication. Use Wait Milliseconds when a workflow should pause for delivery progress. See the documentation

Fetch prior Super Carl communication history for a target before drafting or sending. Use this to avoid duplicate outreach and to inspect recent Gmail, LinkedIn, X, Instagram, and Super Carl sends. See the documentation

Check which Super Carl communication channels are available for a target before sending a message. Returns the list of channels with their can_send status, recipient email, and connector user IDs. Each channel entry carries verbose reason/relationship metadata — pass Fields (e.g. channel, can_send, reason) to keep the result small when you only need the essentials. See the documentation

Cancel a queued or in-progress Super Carl communication. Use this when a workflow needs to stop delivery before the communication reaches a terminal status. See the documentation