Botdog

Create 1 to 100 lead records from LinkedIn profiles in an existing campaign. This changes the campaign's external audience and may cause its configured outreach workflow to act on those leads; it does not create or configure the campaign.

Return outreach analytics for a preset period, either as team/campaign totals or as a per-user breakdown.

Return one campaign's identity, status, owner, and configured dates by campaign ID.

Return a campaign's configured workflow steps and branches in graph, tree, readable, or combined form; this does not edit or launch the campaign.

Return invitation, message, profile-visit, and response metrics and rates for one campaign.

Return the name and user count of the Botdog team authenticated by the connected API key.

Return one outreach-activity row per calendar day plus totals for an explicit date range, optionally filtered by user or campaign.

Return connected LinkedIn sending accounts and their connection health for the authenticated Botdog team.

Return campaigns in the authenticated Botdog team, optionally filtered by status or owner user IDs.

Return one cursor-controlled page of team leads, optionally filtered by campaign, list, campaign state, reply state, unread state, or skip state.

Return Botdog users in the authenticated team so their IDs can be used in campaign and analytics filters.

Immediately send a LinkedIn message to an existing lead conversation, or schedule delivery when send_at is provided. This causes irreversible external LinkedIn delivery and consumes the sending account's daily message budget. Botdog's changelog marks both documented routes as unreleased, and neither route has been live-verified by this integration. Never retry automatically after a timeout, network failure, server error, or other ambiguous result because Botdog may already have accepted the delivery.