CONNECT APP
Build with Close
CRM
- API key
MCP
Give your agent Close tools
Every Close action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Close account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "close",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Lead:
const result = await mcp.callTool({
name: "close-create-lead",
arguments: {
name: "Name",
url: "Url",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "close",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Create Lead:
result = await session.call_tool("close-create-lead", {
"name": "Name",
"url": "Url",
})API PROXY
Call the Close API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Close API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.close.com/api/v1/me/",
})
// Any allowed Close endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.close.com/api/v1/me/
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuY2xvc2UuY29tL2FwaS92MS9tZS8?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Close actions from your backend
Connect a user's Close account once, then run Create Lead on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "close-create-lead",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
close: { authProvisionId: "apn_xxxxxxx" },
name: "Name",
url: "Url",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="close-create-lead",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"close": {"authProvisionId": "apn_xxxxxxx"},
"name": "Name",
"url": "Url",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "close-create-lead",
"configured_props": {
"close": { "authProvisionId": "apn_xxxxxxx" },
"name": "Name",
"url": "Url"
}
}'TOOLS
Close actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Lead
actionCreates a lead. See the documentationWritev0.1.3 -
Custom Action
actionMakes an arbitrary call to the Close API. See the documentation for all options.Writev0.1.3 -
List Lead ID Options
actionRetrieves available options for the Lead ID field.Read-onlyv0.0.1 -
List Status ID Options
actionRetrieves available options for the Status ID field.Read-onlyv0.0.1 -
Search Leads
actionSearch leads with a given field and word. See the documentationWritev0.1.3 -
Update Lead
actionUpdates a lead. See the documentationWritev0.1.3
-
New Custom Event
triggerEmit new event when the configured types of events are triggered. See all possibilitiesInstantv0.1.1 -
New Lead
triggerEmit new event when a new Lead is createdInstantv0.1.1 -
New Lead Status Change
triggerEmit new event when a Lead's status is changedInstantv0.1.1 -
New Opportunity
triggerEmit new event when a new Opportunity is createdInstantv0.1.1
MULTI-APP
Use Close with other popular apps
Most products don't stop at one integration. Pair Close with the other apps your users rely on, and ship use cases that span both.
- App slug
- close
- Authentication
- API key
- Categories
- CRM
- Actions
- 6
- Triggers
- 4
- API proxy
- Available