Nock status
Answered our latest tool-list check 22 hours ago with 101 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 1 of 1 checks
- Last seen working
- 16 Nov, 12:17 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 16 Nov, 12:17 | Answered | 3.0 s | 101 |
Tools (101)
Read from the server on 16 Nov 2026.
- create_sheet
- Creates a NEW empty enrichment sheet owned by the authenticated user and returns its sheetId. mode 'people' is for contacts and 'company' for organizations. A sheet the user already has with the same name and mode is returned instead of creating a duplicate. Sheets can be created here, not only in the dashboard.
- list_sheets
- List the authenticated user's enrichment sheets. Returns each exact sheet id, name, people/company mode, row count, and referenceable columns. Read-only.
- get_sheet_rows
- Reads rows from ONE sheet the user owns. Returns each exact row id plus non-empty cell values with their visible column labels and stable column ids. Reads up to 25 rows at a time with offset/limit, or known rowIds directly. Read-only and free.
- qualify_sheet_leads
- Score people in one owned sheet against the workspace ICP or an explicitly linked campaign audience, using the data and signals Nock already has. Returns fit, priority, coverage, status, evidence gaps and concise explanations per row. Use the active selected rowIds when present; omit rowIds only when the user means the whole sheet. This does not search LinkedIn, Reddit or the open web.
- add_rows_to_sheet
- Add rows to ONE specific enrichment sheet owned by the authenticated user, by its exact sheetId. People and company search results can be passed exactly as returned; nested objects become flat columns. Keys may be stable column ids, semantic keys such as fullName/companyDomain, exact renamed column labels, or new field names. New fields become referenceable columns; matching people/companies keep
- add_enrichment_to_sheet
- Adds and configures one field-specific enrichment column in a sheet the user owns. Inputs are bound to stable column ids, matching exact labels and source keys automatically. When no safe binding exists, it returns the available columns and adds nothing; a retry with inputBindings sets the binding. It configures the column but does not run it, so it spends no credits.
- discover_decision_makers
- Discover a specific decision-maker profile for company rows in an owned company sheet and save them into a people sheet. A dedicated multi-company action, separate from the enrichment-field catalogue. Uses all available company context (name, trade/legal name, domain, corporate email, CNPJ, partners, industry and location), can target selected rowIds or the whole sheet, and can also enrich request
- identify_business
- Find who decides in a SMALL business (a school, a market, a clinic) and how to reach them: name, role, the public origin of each fact (company site, Google Maps, Receita Federal, Instagram…), a work e-mail, the owner's mobile when it can be confirmed. Takes a name and city (and state), or a CNPJ, or a website. Charged only for what is found: 8 credits for a decision maker our search found (site, M
- confirm_decision_maker
- Records whether a decision maker returned by the small-business decision-maker lookup is right, wrong, or has left the business. Free. The verdict weighs on the confidence every workspace sees and, for 'left', the person is no longer offered; the evidence is kept.
- check_whatsapp
- For B2B outreach: tell which Brazilian business mobile numbers the user already has (a company's or a decision maker's, from a sheet or a search) have WhatsApp, so a campaign only writes on WhatsApp to numbers that can receive it. It returns only yes, no or unknown per number: no name, profile or message. Up to 100 numbers per call, in any format. Charged 3 credits per number that has WhatsApp, on
- find_companies_with_rules
- Find companies that meet very specific rules, checked one by one with evidence: e.g. "revendas de peças agrícolas no RS" (source: web search "revenda de peças agrícolas" in RS cities, or the Receita by CNAE 4661300; rules: "vende peças agrícolas, não só máquinas", "é revenda, não fabricante"). Each company's own site (or a web search on it) is read and every rule is judged as met, not met or no ev
- company_group
- The economic group of a Brazilian company by its CNPJ: the companies that control it (its partners that are companies, up to two levels) and the companies its group's head controls (subsidiaries and acquired companies that keep their own CNPJ), each with its CNPJ, legal name, main activity (CNAE) and status at the Receita (inactive ones flagged), plus the group's active factories. Free: registry l
- company_products
- What a Brazilian company sells and how much of it: products registered at the Anvisa across its economic group (registered foods such as supplements, and cleaning products) and the product pages of its own site (pass domain), the product kinds with their usual packaging, and a volume tier (alto, médio, baixo) with why. Free. Answers how many SKUs or products a company has, what kinds, or tiers bra
- feed_campaign_with_signal
- Make a campaign take, every day, the companies a signal monitor finds (including a custom signal monitor, market.category "custom"). The person at each company is the jobTitle given (or the campaign's); a social monitor (engagement with posts) gives the people themselves, no jobTitle. Linking is free; each person is charged as any campaign person when they enter. From then on the campaign enrolls
- import_linkedin_connections
- Warm campaign source: reads the user's own LinkedIn first-degree connections (free, from the LinkedIn account the user connected to Nock; never anyone else's network) into a new people sheet in the user's workspace, newest first, keeping those whose headline has any of the keywords (their ICP's titles or sectors). Only the professional profile LinkedIn shows a connection (name, headline, profile U
- phone_owner
- For B2B outreach: checks that a Brazilian mobile number found for a decision maker (in a sheet or a search) really belongs to that person, before a campaign writes to it, from the owner's name and e-mails the registry has for it. One number per call. Meant only for a business contact the user is already prospecting, not for identifying a private individual. Charged 10 credits only when a name come
- clean_phone
- Fix the format of Brazilian business phone numbers the user already has (a company's or a contact's, e.g. from a sheet) for free: puts them as (DD) NNNNN-NNNN, adds the missing ninth digit of a mobile, and marks a number that cannot exist (an unknown area code, too short). kind is mobile or landline. Up to 500 numbers per call. Formatting only: nothing is looked up outside, and no owner, name or o
- edit_sheet
- Edits a sheet the user owns with the same persistent operations as the dashboard: add custom/AI columns, rename/delete/hide/show/reorder/resize columns, update cells, or delete rows. Takes exact row and column ids.
- select_sheet_rows
- Select up to 25 exact rows in the currently open sheet so the dashboard shows them selected and the same row ids can be used for a campaign later. This changes web UI selection only; it does not delete or modify data.
- export_sheet_csv
- Export an owned enrichment sheet to deterministic UTF-8 CSV in its visible column order. In the dashboard the returned CSV is downloaded automatically.
- run_sheet_enrichment
- Run one already-configured enrichment column and persist its waterfall results in the sheet. Takes the exact enrichment column id (as the sheet's rows list it) and optionally the row ids to process; without them, the first 25 rows that have any value. For several columns pass columnIds: they run in order, company domain, LinkedIn, work e-mail, then phone or WhatsApp, each reading what the one befo
- run_sheet_ai_column
- Runs one already-configured AI or web-research column and saves a generated value for each requested row. Takes the column's exact ai: id and, optionally, the rowIds to run. It costs 1 credit per row for an AI column and 6 per row for a web-research column (aiKind "web", which reads the company's site and searches the web, citing its source); the column's creditsPerRow says which. The result's cre
- search_people
- Search for PEOPLE (potential leads) matching filters such as job title, seniority, company, CNPJ, industry, location or a buyingSignal (hiring, funding, news, job_change, tech, cnpj, crm, visitor, any). Company discover uses the enabled signal sources. job_change is company hire/promote/leave news when those domains exist; otherwise it searches person movers in the last 90 days through enabled sou
- search_companies
- Searches for COMPANIES matching filters such as name, industry, keywords, size, location or businessModel (b2b or b2c). Brazilian searches also support the public company registry: CNAE (activity code), Receita status, headquarters/branch, fiscal size, social capital, legal nature, Simples, opening period, partner name and presence of phone or email. A Brazilian company is identified by its CNPJ,
- list_enrichment_fields
- Lists the enrichment fields currently available in Nock, with the same catalogue, configured-provider filtering, input definitions, provider order and credit prices shown in the dashboard's Tools drawer. Each field id and its inputs are what a single-field enrichment takes. Read-only and free.
- enrich_field
- Enrich ONE specific sheet field for one person/company row. Uses the same field catalogue and provider cascade as the dashboard, stops as soon as that field is found, and returns found/not_found/error deterministically. Valid field ids and their inputs come from the enrichment field catalogue. First it looks the lead up in this workspace (people sheets, campaigns and kept briefs, by email, LinkedI
- enrich_field_batch
- Enrich ONE field for up to 25 people in one call: the same lookup as the single-person enrichment for each person, run on Nock's side 5 at a time, so a list does not wait for one person after another (a mobile can take over a minute a person, so 10 mobiles take about 2 to 3 minutes and 25 about 6). results has one entry per person, in the order sent (index), each with the same fields as the single
- research_web
- Answers a free-form natural-language QUESTION about a single lead/company (e.g. "what does this company sell?", "recent funding?") with web research. Grounds the answer in the company's website when one can be resolved. The answer is AI-generated and may be uncertain; it costs credits. Returns a concise answer plus the source URL used.
- send_to_webhook
- POST JSON to a webhook SAVED in this workspace (n8n, Make, Zapier or the user's own system), once, now. It only sends to webhooks saved in Integrações e MCP → API e webhooks: takes the saved webhook's name or id, not a URL; an address that is not saved is refused, and so is one that is not public https. Takes exactly one of: payload (a JSON object), sheetId (optionally with rowIds) to send that sh
- ai_column
- Generate ONE terse value (a few words / one line) for a row, given that row's known fields and a natural-language instruction — the same "Usar IA" column available in Nock. Use for classification/extraction/summarization into a single cell. A question about facts of the row's company or person (sector, products, news, technology, size, funding) first reads the company's site and runs a short web s
- list_outreach_templates
- Lists the authenticated user's saved outreach templates. Each template carries the reusable campaign configuration: offer, sender name, tone, business/company context and language. Read-only. Only templateIds returned here are valid; a campaign can also be created without a template, from name and offering.
- save_outreach_template
- Create or update one outreach template for the authenticated user. Without templateId the template is saved by name (an existing template with the same name is overwritten with the new values instead of duplicated). With templateId the named template is patched, which is the only way to rename it; the fields passed replace the saved ones and omitted fields keep their current value. An overwritten
- delete_outreach_template
- Delete ONE saved outreach template owned by the authenticated user. Campaigns already created from it are not affected.
- list_outreach_campaigns
- List the authenticated user's prospecting campaigns with their pipeline totals per status, including each campaign's objective (goal) and CTA, so the objectives already running are known. With campaignId it also returns abTests: each cadence step under an A/B test with sends, replies and reply rate per version and the rule that picks the winner. Archived campaigns (status archived: kept with their
- list_outreach_senders
- List the authenticated user's connected outreach senders: Gmail mailboxes, LinkedIn accounts and WhatsApp accounts, with the exact mailboxId / linkedinAccountId / whatsappAccountId other inputs take. Each LinkedIn account sends at most 30 invites and messages a day, shared by every campaign that sends from it, and each campaign at most its own linkedinDailyLimit (20 by default, a campaign setting)
- create_outreach_campaign
- Generate one personalized outreach message per people-sheet row and save them as a new prospecting campaign. Takes the exact sheetId of a people sheet. Without rowIds, uses every people row in that sheet (up to 1000, added in batches of 25 within this one call). templateId must be the exact id of a saved template; otherwise the campaign is described inline with name, offering, goal and a concrete
- generate_outreach_campaign
- Create a new outreach campaign in one go, the dashboard's 'Criar com um clique'. Without sheetId it follows the onboarding's steps with no questions (the best campaign that does not repeat the workspace's, its first 10 people found and saved in a new sheet, billed like any search, and its cadence), and leaves it as a draft to review and activate; it reports its phases while it works. The result's
- update_outreach_campaign
- Edits the settings of ONE outreach campaign the user owns, by campaignId. Only the fields passed change; the others keep their value. Fields: campaign name, offering (what the user's company sells), give (something useful offered before asking for the reader's time, such as a diagnosis, a sample or a draft), sender name, company, role and URL, tone, goal, call to action, message length, constraint
- set_campaign_daily_people
- Changes how many new people an active campaign adds each day (0 turns daily additions off; at most 500). It authorizes spending every day, so it takes two calls: the first, with confirm false, only returns the new monthly credit ceiling and changes nothing; a call with confirm true and that same monthlyCredits applies it. Only a workspace owner or admin can change it. This is people added per day,
- find_people_for_campaign
- Finds NEW people for an existing campaign now and adds them to it ("add 40 more people to this campaign"), from the campaign's saved search or its signal, the same search its daily additions run. People already in the campaign are skipped; each person found goes into the cadence and the campaign's sheet. At most 200 per call; a campaign has no size limit. It spends credits, so it works in two call
- set_campaign_signal_monitor
- Feeds a campaign from a market signal monitor, or stops it with monitorId null. Each day the campaign's daily additions take the companies the monitor delivered and write to one person at each: the person the monitor already found, a store's owner, or jobTitle searched at the company (required unless the monitor is about online stores or the campaign already has a job title). It spends nothing by
- update_outreach_cadence
- Changes the cadence of ONE campaign: the shared template every person gets, and people added later. A change of form or tone (lowercase, more formal, shorter, another greeting, no emoji) applies to every step. A change of content or structure (add a question, mention something, change the argument) applies to the step it points to (a day, a channel, a sentence only that step has), not to every ste
- regenerate_outreach_cadence
- Rewrites the open (unsent) cadence messages of people in ONE campaign with the AI writer, from the campaign's current template. It takes no instructions and does not change the template or a step's text or day. Steps that already sent, failed, or are mid-dispatch are kept. Optional prospectIds limit the rewrite to those people; without them everyone with unsent steps is refreshed. Nothing is sent.
- adjust_outreach_cadence
- Changes how ONE campaign's messages read from one sentence of the user ('não fala de preço na primeira mensagem', 'mais curto', 'sem link na primeira', 'muda o tom para mais direto') and writes its template again in the same shape, now (it takes a few seconds). The people's steps not sent yet take the new template; nobody's messages are written again until a rewrite is requested (messagesNext in t
- update_cadence_ai_field
- Changes the instruction of one sentence the Agent writes for each person in ONE campaign's cadence (a field marked {{ia:key}} in the bodies, shown on screen by its label, such as 'a vaga aberta' or 'a retomada'), for everyone on the list: how that sentence should read for all people ('na abertura, começa com "vi que vocês abriram vaga de X"', 'na vaga aberta, cita o cargo da vaga', 'a retomada não
- list_cadence_versions
- List the earlier versions of a campaign's cadence template, newest first: when each was replaced and the start of each step. Every change to the template keeps the version it replaced (up to 30). For getting an earlier version back or seeing what changed.
- restore_cadence_version
- Puts an earlier cadence template back ("volta pro template que tava antes"). Without versionId it restores the most recent earlier version; versionId picks another. Steps already sent stay; people who have not received a step get the restored template, but their messages are not rewritten by this call: the result's messagesOutdated counts them and messagesNext describes the rewrite still pending.
- preview_campaign_messages
- Writes the messages of ONE example person of the campaign from its current template and returns them, to show how the template reads before the other people's messages are written again. Not read-only: the new messages replace that person's unsent ones (sent and hand-edited messages are kept). Nothing is sent to anyone. It picks the person itself (one with a buying signal when there is one) and ke
- rewrite_campaign_messages
- Writes again the messages of the people of ONE campaign that are from an earlier version of its template (messagesOutdated), the "Reescrever as N" action. One run, only those people: sent messages and hand-edited ones stay. It is refused in the same request that changed the template. Free. Nothing is sent. Returns how many were rewritten, or that the rest is still being written.
- add_prospects_to_campaign
- Add people from a people sheet to an existing campaign. Fills the campaign's cadence template with each person's name, company, role and signals. Skipped: rows already in the campaign; people the user's connected CRM already has (the result's crmKnown, with crmKnownReason saying how many and why); and people the user removed from this campaign before (the result's removedBefore, with removedBefore
- activate_outreach_campaign
- Activate the automatic cadence of ONE draft campaign. Fills the campaign's cadence template with each person's name, company, role and signals into its steps (by default a LinkedIn connection and message first, then e-mail, alternating) and sends them through the selected connected Gmail, LinkedIn and/or WhatsApp accounts. When several accounts are connected on a channel, the account id for that c
- update_outreach_campaign_status
- Pause or resume ONE campaign cadence, or archive it. Pausing prevents new sends and freezes the schedule. Resuming may send the next due step immediately when inside the business window. "archived" keeps the people, the sends, the replies and the reports, stops everything and takes it out of the campaign list; "paused" on an archived campaign unarchives it (paused, or a draft when it never ran). A
- list_prospects
- Lists the authenticated user's prospects (people with a generated message) with their pipeline status, optionally filtered by campaign or status. Returns a compact summary, without the full message and history.
- get_prospect
- Get ONE prospect owned by the authenticated user: the full LinkedIn connection note, the email subject and body, the captured sheet context and the activity history (generation, edits, status changes).
- update_prospect
- Update ONE prospect owned by the authenticated user: move it through the pipeline and/or rewrite its message. Editing a message never regenerates it and never costs credits. Statuses: ready, sending, awaiting_reply, replied, paused, failed. Setting awaiting_reply stamps the sent time; replied stamps the reply time.
- delete_prospect
- Delete ONE prospect owned by the authenticated user, including its messages and history. The campaign remains even if it has no people left. Irreversible: it cannot be undone.
- disqualify_prospect
- Take ONE person out: scope "campaign" removes them from this campaign's cadence; scope "list" also removes them from the people sheet they came from. Unsent steps stop.
- set_prospect_closure_reason
- Record why a conversation with ONE person ended (interested, not_interested, bad_timing, has_solution, wrong_person, opt_out), or null to clear it. Kept as history; it does not send anything.
- activate_prospect_channel
- Look up the missing work e-mail (channel email) or LinkedIn profile (channel linkedin) of ONE person in a campaign and, when one is found, turn that channel on in the person's cadence. This call sends nothing; the cadence sends on its schedule. Charges enrichment credits only when a contact is found.
- send_prospect_step_now
- Sends ONE step of ONE person's cadence right now, ahead of its schedule. This sends a real message to the prospect. Runs only with confirmed: true. stepIndex is the 0-based position in that person's cadence.
- brief_lead
- The platform's person and company brief for one lead: who they are now (LinkedIn read today), their role at the company, what they post about, and their company (what it sells, customers, size, funding, open roles, key points, news, its posts, competitors). Takes an email, the person's LinkedIn URL, a company domain or the company's LinkedIn URL (any one is enough; more make it surer). Costs 22 cr
- find_lead
- Where a lead already is in this workspace and what is known about them: the people sheets whose rows match (with that row's fields, which may already hold the answer without enriching), the campaigns they are in and the briefs already made about them (who they are, title, LinkedIn, company). Pass an email, a LinkedIn URL, a name or a company. Free.
- list_inbox_conversations
- List the Inbox conversations with campaign people, newest first: who replied, the last message preview and any step waiting for approval (pendingApproval). Optional filters narrow to replies, pending approvals or one campaign.
- get_inbox_conversation
- Read one Inbox conversation (every message both ways) with a campaign person on one channel.
- approve_inbox_message
- Approves and sends the step waiting for approval in one Inbox conversation (campaigns set to approve before sending). This sends a real message to the prospect. Runs only with confirmed: true. stepIndex comes from the conversation's pendingApproval.
- motor_report
- Reports the results of each outreach campaign in the workspace (people contacted, replies, meetings, credits spent); Nock calls each campaign with its signals a "motor", a prospecting playbook. Read-only. How the motors are doing ("como estão os motores?"): every campaign of the workspace as a motor, for the last 7, 30 or 90 days. Per motor: people added, people first contacted in the period, repl
- explore_signals
- Search a buying signal like the Sinais screen: companies hiring a role (hiring), recent funding rounds (funding), company news (news), companies showing a technology (tech), Brazilian company registry events (cnpj), closed-lost CRM deals (crm) or people new in a role (job_change: jobTitle, periodDays 30/60/90, location, industry, companySizes; domains narrows to the user's accounts for "decisor no
- list_signal_monitors
- List the workspace's signal monitors: category, filters, status, schedule and monthly credit limit.
- create_signal_monitor
- Creates a signal monitor. Default: a MARKET monitor, with no source sheet: { mode: 'market', name, market: { category, ...filters }, dailyLimit }. Every day (or week) it searches the signal over that market and saves only companies it has not delivered yet into a companies sheet, created with the monitor's name unless destinationSheetId is given. Market categories: hiring needs hiringTitle, and in
- update_signal_monitor
- Change a signal monitor: its filters, name, schedule, monthly credit limit, destination sheet, or pause/resume it. Only the fields sent change. A market monitor also takes dailyLimit and market (its whole filter set, same signal). An engagement signal takes addPeople and removePeople (LinkedIn profile URLs; a founder found on its own can be removed too); its watchedProfiles say whose posts it read
- run_signal_monitor
- Run a signal monitor now instead of waiting for its schedule. Spends from its monthly credit limit.
- list_signal_events
- Read saved signal events, from one monitor or the whole workspace, newest first.
- export_signal_events
- Save events of one monitor, by their event ids, into a company or people sheet. Repeated events are skipped.
- list_received_invitations
- List the LinkedIn connection requests the user's connected account received: who asked to connect, their headline and what they wrote. Someone from the ICP who asked to connect is a warm lead. Read only and free; accepting a request is not done by this tool. If the workspace has several LinkedIn accounts, pass accountId.
- accept_received_invitation
- Accepts ONE LinkedIn connection request that the user's connected LinkedIn account received. It acts on the user's own LinkedIn account and runs only with confirmed true. One invitation per call.
- update_campaign_settings
- Changes a campaign's sending rules; only the fields sent change. approveBeforeSending can only be turned on here (every step then waits for approval in the Inbox); turning it off, and the daily enrollment, are authorizations given in the campaign's Settings screen. Turning off blockActiveSequence or blockContactedBefore returns a warning with what the campaign then lets in. Free. Nothing is sent.
- read_learn_article
- Read Nock's own tutorials (the Aprender page): how something in Nock works, what it costs or where to find it. With slug: the whole tutorial. With query (or nothing): the tutorials that match, with their slugs. Each tutorial's page is /aprender/<slug>. Read-only, free.
- get_customer_list
- Read the workspace's customer list: companies that are already customers. Nobody at them gets a first message and searches leave them out.
- update_customer_list
- Change the workspace's customer list. mode add puts companies on it, remove takes them off, replace swaps the whole list (only when the user sends their full list). lines: one company name or site per line, or "Name, site".
- get_knowledge_base
- Read the workspace's company profile (what it sells, ICP, persona, pains, competitors, exclusions), its documents, and what you learned in earlier conversations (memories, each with its id).
- update_knowledge_base
- Change the workspace's company profile. Only the fields sent change; send the full new text of a section you rewrite. Campaigns written afterwards use it.
- add_knowledge_document
- Add a text document to the workspace (a pitch, a case, a price list) so campaigns can use it.
- remove_knowledge_document
- Remove one workspace document, by its id, from the workspace's knowledge base. It cannot be undone.
- add_cadence_rule
- Saves one workspace rule for how messages read, in the user's words: tone, wording, language, what never to claim, price, links, what to say first (e.g. "nunca fale de preço na primeira mensagem", "sempre em português", "não cite concorrentes"). Every cadence written afterwards follows it; existing cadences change only when rewritten. The number of steps, their days and channels are campaign setti
- remove_cadence_rule
- Take one rule out of the workspace's cadence rules, for example a rule just kept from a cadence adjustment (its keptRules) that was meant for one campaign only or no longer holds. Takes the rule's text as it was kept. Campaigns already written keep their text; the next ones stop following it. Free.
- brain_lookup
- Searches the user's own Nock workspace (not the web) for a company, a person or a subject, read-only, across everything at once: people in campaigns (status, last send, reply), campaigns, sheets (by name or a row that mentions it), signals, the company documents and saved memories. Answers questions about something by name ("tudo sobre a Acme", "o que aconteceu com o Marcos", "o que a gente já fal
- save_memory
- Keep something the user asked to be remembered ("lembra que...", "a partir de agora...") for every later conversation. One sentence each, in their words. Not for the company profile (what it sells, the ICP) nor for how messages must read ("nunca fale de preço", "sempre em português"): those are kept in the knowledge base and the cadence rules.
- forget_memory
- Forget saved memories of the workspace ("esquece isso"), by their memory ids as the knowledge base lists them. They are removed.
- create_routine
- Schedule something the Nock Agent does on its own, every week or every day ("toda segunda, ache 50 decisores novos e coloque na campanha X"), Brasília time. Actions: campaign_add_people (find count new people for a campaign from its search or signal), campaign_refill_from_signal (run the campaign's signal and add count people), campaign_status (pause or resume a campaign), sheet_enrichment (run an
- list_routines
- List the workspace's routines (what runs, when, the credit cap, active or paused, next run), the autonomy level of each action type, and the last actions the Nock Agent took or suggested. Free.
- set_routine_status
- Pause a routine, or resume it (it runs again at its next slot, never the ones it missed).
- delete_routine
- Delete a routine for good. Two steps: with confirmed false it only returns which routine would be deleted and changes nothing; with confirmed true it deletes it, which cannot be undone. Pausing a routine is the reversible alternative.
- set_autonomy_level
- Set how much the Nock Agent does alone for one action type in this workspace: 1 only tells, 2 suggests and does it with one tap (default), 3 does it and tells after. Whatever the level, the Agent still waits for approval before spending above a routine's credit cap, deleting, messaging leads with a cadence nobody approved, or touching billing. For an explicit request to change how much the Agent m
- rename_sheet
- Rename one owned sheet.
- duplicate_sheet
- Copy one owned sheet, rows and columns, under a new name.
- delete_sheet
- Deletes one owned sheet and all its rows. This cannot be undone. Requires confirmed: true.
- restore_company_sheet
- Turn a sheet that a campaign converted from companies into people back into the company sheet it was: each company once, with its columns; the decision makers found there are removed from the sheet (the campaign keeps its people). Runs only with confirmed: true. Refused while someone from the sheet is in an active campaign.
- get_credit_balance
- The workspace's credits now: how many are available to spend, how many are held by operations still running, and the plan. Answers how many credits the workspace has and whether an action fits the balance. Free and read-only.
- install_site_tracker
- Creates or changes the workspace's website tracker (the 'Visitou seu site' signal) and returns the install snippet: two script lines the customer puts before </head> on every page of their site, the domains it accepts visits from (the workspace's site by default), and a default paragraph for their privacy policy. The script identifies the COMPANY behind a visit by its network (not the person); a p
- list_site_visitors
- Companies that visited the workspace's website (through the workspace's site tracker), strongest first: pages and sessions, whether they saw prices or a demo, first and last visit, people who identified themselves, and a strength 0-100 (recency, frequency, buying pages). Free. Meant as timing: messages do not mention the visit unless the workspace turned citeVisits on.
- send_feedback
- Shares feedback about Nock with the Nock team: product feedback from the user (praise, a complaint, something missing) or something concrete observed in Nock that worked or failed (a tool returned wrong or empty data, a step was confusing, a result was great). Not for model behavior, the user's local environment, an unclear prompt, or a tool error that was recovered from. actor "human" is for the