CONNECT APP
Build with Nextdoor Ads
Marketing
- API key
MCP
Give your agent Nextdoor Ads tools
Every Nextdoor Ads 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 Nextdoor Ads 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": "nextdoor",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Create Ad:
const result = await mcp.callTool({
name: "nextdoor-create-ad",
arguments: {
advertiserId: "Advertiser ID",
campaignId: "Campaign ID",
},
})# 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": "nextdoor",
}
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 Ad:
result = await session.call_tool("nextdoor-create-ad", {
"advertiserId": "Advertiser ID",
"campaignId": "Campaign ID",
})API PROXY
Call the Nextdoor Ads API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Nextdoor Ads 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://ads.nextdoor.com/v2/api/me",
})
// Any allowed Nextdoor Ads 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://ads.nextdoor.com/v2/api/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hZHMubmV4dGRvb3IuY29tL3YyL2FwaS9tZQ?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Nextdoor Ads actions from your backend
Connect a user's Nextdoor Ads account once, then run Create Ad 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: "nextdoor-create-ad",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
nextdoor: { authProvisionId: "apn_xxxxxxx" },
advertiserId: "Advertiser ID",
campaignId: "Campaign ID",
},
})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="nextdoor-create-ad",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"nextdoor": {"authProvisionId": "apn_xxxxxxx"},
"advertiserId": "Advertiser ID",
"campaignId": "Campaign ID",
},
)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": "nextdoor-create-ad",
"configured_props": {
"nextdoor": { "authProvisionId": "apn_xxxxxxx" },
"advertiserId": "Advertiser ID",
"campaignId": "Campaign ID"
}
}'TOOLS
Nextdoor Ads actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Create Ad
actionCreates an ad based on the input payload for an existing NAM ad group. See the documentation.Writev0.0.2 -
Create Ad Group
actionCreates an ad group based on the input payload for an existing campaign. See the documentation.Writev0.0.2 -
Create Advertiser
actionCreates an advertiser that is tied to the NAM profile the API credentials are tied to. See the documentation.Writev0.0.2 -
Create Campaign
actionCreates a campaign. See the documentation.Writev0.0.2 -
Create Scheduled Report
actionCreates a scheduled report based on the input configuration. Upon a successful request the report will be sent out based on the schedule cadence. See the documentation.Writev0.0.2 -
List Advertiser ID Options
actionRetrieves available options for the Advertiser ID field.Read-onlyv0.0.1 -
List Category ID Options
actionRetrieves available options for the Category ID field.Read-onlyv0.0.1
EVENTS
Nextdoor Ads triggers
Event sources your backend can deploy for users and receive through a webhook.
No Nextdoor Ads triggers are available yet.
MULTI-APP
Use Nextdoor Ads with other popular apps
Most products don't stop at one integration. Pair Nextdoor Ads with the other apps your users rely on, and ship use cases that span both.
- App slug
- nextdoor
- Authentication
- API key
- Categories
- Marketing
- Actions
- 7
- Triggers
- 0
- API proxy
- Available