CONNECT APP
Build with Survicate
Help Desk & Support
- API key
MCP
Give your agent Survicate tools
Every Survicate 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 Survicate 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": "survicate",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Delete Personal Data:
const result = await mcp.callTool({
name: "survicate-delete-personal-data",
arguments: {
email: "Email",
},
})# 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": "survicate",
}
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 Delete Personal Data:
result = await session.call_tool("survicate-delete-personal-data", {
"email": "Email",
})API PROXY
Call the Survicate API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Survicate 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://data-api.survicate.com/v1/surveys",
})
// Any allowed Survicate 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://data-api.survicate.com/v1/surveys
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9kYXRhLWFwaS5zdXJ2aWNhdGUuY29tL3YxL3N1cnZleXM?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Survicate actions from your backend
Connect a user's Survicate account once, then run Delete Personal Data 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: "survicate-delete-personal-data",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
survicate: { authProvisionId: "apn_xxxxxxx" },
email: "Email",
},
})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="survicate-delete-personal-data",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"survicate": {"authProvisionId": "apn_xxxxxxx"},
"email": "Email",
},
)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": "survicate-delete-personal-data",
"configured_props": {
"survicate": { "authProvisionId": "apn_xxxxxxx" },
"email": "Email"
}
}'TOOLS
Survicate actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Delete Personal Data
actionDeletes personal data associated with an email address for GDPR compliance. See the documentationWritev0.0.1 -
Get Personal Data Counters
actionRetrieves counts of personal data records for GDPR compliance. See the documentationRead-onlyv0.0.1 -
Get Response
actionRetrieves detailed information about a specific response. See the documentationRead-onlyv0.0.1 -
Get Survey
actionRetrieves detailed information about a specific survey. See the documentationRead-onlyv0.0.1 -
List Questions
actionRetrieves a list of questions for a specific survey. See the documentationRead-onlyv0.0.1 -
List Respondent Attributes
actionRetrieves the names and values of custom attributes associated with a specific respondent, which have been passed to Survicate through the JavaScript API, integrations, or embedded within the survey link. See the documentationRead-onlyv0.0.1 -
List Respondent Responses
actionRetrieves a list of survey responses provided by a specific respondent identified by their unique identifier (UUID). See the documentationRead-onlyv0.0.1 -
List Responses
actionFetches the list of responses for a specific survey identified by its unique ID. See the documentationRead-onlyv0.0.1 -
List Surveys
actionRetrieves a list of all surveys from your workspace. See the documentationRead-onlyv0.0.1
EVENTS
Survicate triggers
Event sources your backend can deploy for users and receive through a webhook.
No Survicate triggers are available yet.
- App slug
- survicate
- Authentication
- API key
- Categories
- Help Desk & Support
- Actions
- 9
- Triggers
- 0
- API proxy
- Available