Nextdoor Ads
Answered
Which application or service?: Nextdoor Ads
What type of connector? (SaaS, Database, File or Event Source):
Saas or api based ad performance tables.
Additional details:
Nextdoor launched its Ads API program in April 2024 and it covers what a connector would need: campaign, ad group, and ad management objects plus reporting endpoints for performance over time. Docs are public at https://developer.nextdoor.com/docs/advertising-overview, and API tokens are self-serve from the Nextdoor Ads Manager settings page, so auth looks straightforward (token based, no OAuth app review).
Questions:
- Is a Nextdoor Ads connector already on the roadmap? If so, is there a timeline we can plan around?
- If it isn't, what's the best way to get it considered? We're happy to detail the tables and grain we'd want (daily spend, impressions, and clicks at campaign, ad group, and ad level, consistent with your other ads connectors).
- If a beta or early access program comes up for it, we'd like to be included.
-
Official comment
Hi Derrick,
Thanks for the request!
For REST-based sources like Nextdoor Ads, the best path today is Fivetran AI Connector Agent. It generates a fully managed Fivetran connector – no code to write, no infrastructure to maintain, and we host and monitor it for you. You can find the quick setup guide here: https://fivetran.com/docs/connectors/ai-connector-agent
Getting started is simple:
Point AI Connector Agent to publicly accessible API documentation (a docs site, OpenAPI / Swagger spec, or even a PDF).
If a formal spec is not available, you can upload a short document that lists the endpoints, auth method, and sample responses you need.
Follow the guided flow to generate and deploy the connector.
If anything is unclear or you run into errors, open a Fivetran Support ticket and we will troubleshoot and advise on next steps.
Please let us know if you run into any blockers.
Thanks
Tom
Please sign in to leave a comment.
Comments
1 comment