CONNECT APP
Build with Seven
Communication
- OAuth
MCP
Give your agent Seven tools
Every Seven 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 Seven 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": "seven",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Get Analytics:
const result = await mcp.callTool({
name: "seven-get-analytics",
arguments: {
start: "Start Date",
end: "End Date",
},
})# 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": "seven",
}
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 Get Analytics:
result = await session.call_tool("seven-get-analytics", {
"start": "Start Date",
"end": "End Date",
})API PROXY
Call the Seven API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Seven 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://oauth.sms77.io/me",
})
// Any allowed Seven 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://oauth.sms77.io/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9vYXV0aC5zbXM3Ny5pby9tZQ?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Seven actions from your backend
Connect a user's Seven account once, then run Get Analytics 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: "seven-get-analytics",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
seven: { authProvisionId: "apn_xxxxxxx" },
start: "Start Date",
end: "End Date",
},
})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="seven-get-analytics",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"seven": {"authProvisionId": "apn_xxxxxxx"},
"start": "Start Date",
"end": "End Date",
},
)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": "seven-get-analytics",
"configured_props": {
"seven": { "authProvisionId": "apn_xxxxxxx" },
"start": "Start Date",
"end": "End Date"
}
}'TOOLS
Seven actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Get Analytics
actionRetrieve account statistics (SMS, RCS, voice, HLR, usage). See the documentationRead-onlyv0.0.2 -
List Subaccounts Options
actionRetrieves available options for the Subaccounts field.Read-onlyv0.0.1 -
Lookup CNAM
actionLook up caller name information via Seven. See the documentationRead-onlyv0.0.3 -
Lookup Format
actionLook up phone number formatting via Seven. See the documentationRead-onlyv0.0.3 -
Lookup HLR
actionLook up home location register information via Seven. See the documentationWritev0.0.3 -
Make TTS Call
actionMake a text-to-speech call via Seven. See the documentationWritev0.1.1 -
Send SMS
actionSend SMS via Seven. See the documentationWritev0.0.3
- App slug
- seven
- Authentication
- OAuth
- Categories
- Communication
- Actions
- 7
- Triggers
- 2
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Seven OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- analytics
- balance
- contacts
- lookup
- hooks
- sms
- status
- subaccounts
- voice