[ACTION] [App] Ringba — request for additional pre-built components

Background

The current Ringba integration on Pipedream provides OAuth auth but no pre-built actions or sources beyond the generic GET /v2/ringbaaccounts example. To use Ringba in workflows today, every step has to be a custom HTTP request, which also means none of these endpoints are exposed via Pipedream's MCP server for LLM-driven automation.

I work in ad ops at a performance marketing company that runs significant pay-per-call volume through Ringba, and I'd like to use Pipedream (and the Pipedream MCP) to automate routine reporting, audits, and configuration tasks. Below are the components that would unlock the highest-value workflows for our team. Most are read-only; a handful of write actions are flagged.

Requested components

Call data & reporting (read)

• List call logs (POST /{accountId}/calllogs) with filters for date range, campaign, publisher, target, and tag values
• Export call log to CSV (POST /{accountId}/calllogs/export)
• Get call detail by call ID
• List/export RTB bid requests (POST /{accountId}/rtb/export/csv + GET /{accountId}/rtb/export/{id})

Campaigns (read + selective write)

• List campaigns
• Get campaign by ID (full settings, including routing plan, targets, numbers)
• Write: pause / activate campaign

Publishers (read + selective write)

• List publishers
• Get publisher by ID (payout settings, status, assigned campaigns)
• Write: update publisher payout
• Write: enable / disable publisher on a campaign

Targets / buyers (read + selective write)

• List targets
• Get target by ID (caps, schedule, payout, routing)
• Write: update target caps (concurrency, daily/monthly cap)
• Write: enable / disable target

Numbers (read)

• List numbers
• Get number by ID (campaign assignment, status)
• List number pools

Tags & routing (read)

• List tags / tag values
• Get routing plan for a campaign

Annotations / post-call data (write)

• Add annotations to a call (POST /{accountId}/calls/{callId}/annotations) — for pushing buyer disposition or downstream conversion data back into Ringba

Why this matters

Ringba's API surface is broad and well-documented (https://developers.ringba.com), and most of these endpoints are simple authenticated REST calls. Having them as first-class Pipedream components would:

1. Let non-developers on ad ops / account management teams build workflows without writing custom code for every step
2. Expose them through the Pipedream MCP, so Claude and other LLM clients can pull Ringba data and audit configurations conversationally — this is the primary use case I'm trying to enable
3. Standardize auth and pagination handling across the Ringba ecosystem on Pipedream

Happy to provide more detail on any specific endpoint or use case if it's helpful for prioritization. Framing this as roadmap input rather than a blocker — we have workarounds today, but native components would make these workflows much more accessible.

Thank you, Paul Hardebeck