CONNECT APP
Build with 4Dem (OAuth)
Marketing
- OAuth
MCP
Give your agent 4Dem (OAuth) tools
Every 4Dem (OAuth) 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 4Dem (OAuth) 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": "_4dem",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Confirm Email:
const result = await mcp.callTool({
name: "_4dem-confirm-email",
arguments: {
senderId: "Sender ID",
authCode: "Auth Code",
},
})# 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": "_4dem",
}
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 Confirm Email:
result = await session.call_tool("_4dem-confirm-email", {
"senderId": "Sender ID",
"authCode": "Auth Code",
})API PROXY
Call the 4Dem (OAuth) API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the 4Dem (OAuth) 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.4dem.it/senders/email",
})
// Any allowed 4Dem (OAuth) 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.4dem.it/senders/email
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuNGRlbS5pdC9zZW5kZXJzL2VtYWls?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run 4Dem (OAuth) actions from your backend
Connect a user's 4Dem (OAuth) account once, then run Confirm Email 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: "_4dem-confirm-email",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
_4dem: { authProvisionId: "apn_xxxxxxx" },
senderId: "Sender ID",
authCode: "Auth Code",
},
})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="_4dem-confirm-email",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"_4dem": {"authProvisionId": "apn_xxxxxxx"},
"senderId": "Sender ID",
"authCode": "Auth Code",
},
)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": "_4dem-confirm-email",
"configured_props": {
"_4dem": { "authProvisionId": "apn_xxxxxxx" },
"senderId": "Sender ID",
"authCode": "Auth Code"
}
}'TOOLS
4Dem (OAuth) actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Confirm Email
actionConfirm sender email address. See the documentationWritev0.0.2 -
Create Email
actionCreate a new email. See the documentationWritev0.0.2 -
Create Sender
actionCreate an email sender. You will need to confirm the email address used during creation. See the documentationWritev0.0.2 -
List Sender ID Options
actionRetrieves available options for the Sender ID field.Read-onlyv0.0.1
EVENTS
4Dem (OAuth) triggers
Event sources your backend can deploy for users and receive through a webhook.
No 4Dem (OAuth) triggers are available yet.
- App slug
- _4dem
- Authentication
- OAuth
- Categories
- Marketing
- Actions
- 4
- Triggers
- 0
- API proxy
- Available