With write access enabled, your AI assistant can act on what it finds in Knock2 — the same actions available as buttons in your dashboard. This article covers each action category, what it needs to work, what it costs, and the guardrails that keep automation safe.
Write access is granted by a workspace admin — see Connecting Knock2 to AI Tools (MCP).
One-off email & LinkedIn outreach
Outreach is always a two-step flow: your assistant drafts a message first (using the contact's activity for personalization if you ask), and sending is a separate, explicit step — so there's always a reviewable draft before anything goes out. Sent messages appear in your Outbound conversations like any other touch.
Email requires your own email account to be connected to Knock2 — sends go from your mailbox. If it isn't connected, you'll be told before anything is created.
LinkedIn can check whether you're already connected with a contact, send a connection request (with an optional note), and send messages or InMail. The contact needs a LinkedIn URL on file.
If a contact is missing the email or LinkedIn URL a channel needs, the draft is refused up front with a suggestion to enrich the contact first — no dead drafts land in your queue.
Adding contacts to your outreach tools
Your assistant can enroll contacts into your connected Apollo, Lemlist, Outreach, HeyReach, or Amplemarket sequences and campaigns — and it can list them by name first, so "add Jane to the onboarding campaign" just works without you hunting for IDs. Any teammate's connection backs the whole workspace: you don't need to have connected the tool yourself.
Pushing contacts to your CRM
Create or update records in HubSpot, Salesforce (as Leads or Contacts), Unify, or Attio — including company details like industry, employee count, and revenue. HubSpot needs a company domain on file to match or create the company; if it's missing you'll be prompted to enrich first. You can also refresh CRM deal data for an account on demand.
Discovering the buying committee
Ask your assistant to run buying committee on any account and Knock2 will search for the decision-makers and influencers matching the roles configured in your Settings — skipping roles already covered and never re-adding people you already have, so repeated runs surface additional people. Found contacts are saved as regular Knock2 contacts, ready to enrich, email, sequence, or push to your CRM.
This also chains: "Run buying committee for every account that scored over 70 this month."
Notifications & data quality
Slack — post a contact card to your connected channel.
Webhooks — send contact data to any webhook (for example, a Zapier hook).
Enrichment — fill in a contact's or account's missing details from what's already on file (an email or LinkedIn URL for contacts; a LinkedIn URL for accounts).
Email validation — check the deliverability of a contact's email and record the result.
What actions cost
Most actions are free. The data actions use your workspace's Knock2 credit balance:
Buying committee: 2 credits per new contact found. A run that finds nothing new costs nothing.
Enrichment: 1 credit per successful enrichment. A no-match attempt is free.
Email validation: 0.5 credits per validation.
Your assistant can answer "what does this cost?" and "how much have I used today?" directly — just ask.
Daily limits & guardrails
Every action type has a daily cap so automation can never run away with your outreach. Limits reset at midnight UTC, and failed actions don't count — only actions that actually happen use up a unit.
Email sends: 50/day
LinkedIn actions: 25/day (deliberately the strictest)
Message drafts: 200/day
Sequence/campaign adds: 200/day
CRM pushes: 100/day
Slack/webhook notifications: 100/day
Enrichments & validations: 200/day
Buying-committee runs: no daily cap — governed by your credit balance instead.
On top of Knock2's limits, clients like Claude show every action individually in the connector's permission settings, so you can set each one to always allow, ask every time, or deny. And every action is attributed to the user whose connection performed it, and logged.
If an action is blocked
"This action requires the '…' permission" — your connection is read-only for that category. A workspace admin can grant it (see the connection article).
"Outbound messaging isn't enabled on your Knock2 plan yet" — email/LinkedIn touches require the Outbound product. Contact support@knock2.ai to get access.
"Contact has no email / LinkedIn URL on file" — enrich the contact first, then retry.
"Daily quota exceeded" — that action type is done for the day; it resets at midnight UTC.
Questions?
Message us in Intercom or email support@knock2.ai.