What does a connection authorize?
- Authentication: identify the account or server you intend to connect.
- Record review: inspect the available records, fields, and their dates, then approve a bounded selection.
- AI permission: separately decide whether approved context may inform supported analysis.
- External action: review the exact supported write and destination before dispatch.
These are distinct decisions. Signing into a provider does not approve all its records, sharing a record does not authorize an external write, and a credential refresh does not make business data current.
CRM connection scope
Feedsion has connection workflows for HubSpot, Zoho CRM, and Attio. Availability depends on the provider, account tier, authentication method, module, and selected fields. An available connector is not a promise that every account or workflow is supported.
Before planning a rollout, tell us the exact provider and workflow. Confirm the record types, required permissions, refresh behavior, and any provider limits. Company-owned connections require separate company authority and approval.
Two directions of MCP access
Bring context into Feedsion
A customer-configured Model Context Protocol (MCP) connection points Feedsion at a server you choose and authorize. The available tools, record schema, and authentication determine what can be reviewed. A server connection does not grant blanket access to your other systems.
Read Feedsion from another client
Feedsion’s read API and MCP interface expose authorized content through scoped credentials. What a client can read still depends on the owner’s current permissions. Read access does not grant generation, publication, or write authority.
MCP support alone does not establish compatibility with every ChatGPT, Claude, Gemini, or other client. Confirm the client’s connection method and the exact Feedsion workflow before relying on it.
Can I start without a CRM?
Yes. Start with a company sentence, a current question, and the constraints you choose to share. Manual context is useful when a connection would add unnecessary records or setup. The sample workspace requires no external credentials.
What happens when access changes?
Paused, withdrawn, expired, or unavailable context must not appear ready for new use. Cleanup and disconnect remain distinct from approving a replacement connection. Review status in your workspace rather than assuming an old sign-in is still sufficient.
Compare connection limits and current availability, or see how context fits into a decision brief.