CRM & Sales
Connect Pushpay ChMS (v1)
Read and update Pushpay ChMS (v1) contacts, deals, and pipeline data.
CRM & Sales
Pushpay ChMS (v1)
Read and update Pushpay ChMS (v1) contacts, deals, and pipeline data.
Basic authScoped proxy
Connect with basic credentials
The client enters the required username, token, or secret pair in the hosted connect flow. CybrLink keeps credentials out of the agent and enforces provider scope before proxy execution.
Where to get your Pushpay ChMS (v1) API keyStep 1
Open the portal connect flow
Step 2
Enter provider credentials
Step 3
Limit write scope before launch
Sample request
// 1. Mint a session token for the end user
const session = await link.connect.session({
integrationKey: "pushpay-chms-v1",
userId: "u_42",
});
// 2. After the user enters their provider credentials, proxy a request
const res = await link.proxy("pushpay-chms-v1", "u_42", {
method: "GET",
endpoint: "/api/v1/me",
});More in this category
Pushpay ChMS (v1) + AI agents: common questions
- How do I connect Pushpay ChMS (v1) to an AI agent?
- Create a free CybrLink account, open the dashboard, and click Connect on Pushpay ChMS (v1). You authorize once with basic credentials; CybrLink stores the credential in its token vault and your agent reaches Pushpay ChMS (v1) through the CybrLink MCP server or the agent proxy API. The credential itself is never placed in the model's context.
- Does Pushpay ChMS (v1) work with Claude, GPT, and other MCP clients?
- Yes. CybrLink exposes a remote MCP (Model Context Protocol) server, so any MCP-capable client or agent framework — including Claude, OpenAI-based agents, and custom agents — can call Pushpay ChMS (v1) once you've connected it. Non-MCP agents can use the authenticated HTTP proxy instead.
- Is it safe to give an AI agent access to Pushpay ChMS (v1)?
- CybrLink scopes every connection to the permissions you grant, keeps tokens out of the model, logs each call to an activity audit trail, and lets you revoke the Pushpay ChMS (v1) connection at any time from the dashboard.