Sendspark MCP integration for AI agents.
Connect AI agents to Sendspark through 5 structured actions, including get dynamic campaign, add prospect, and create dynamic campaign. Review authentication…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Sendspark integration exposes
The Sendspark Agent App exposes 5 provider-backed actions for marketing and design & media work. Its current contract lets an authorized agent get one sendspark dynamic video campaign by workspace and campaign id, add a prospect to a sendspark dynamic video campaign, and create a sendspark dynamic video campaign in a workspace. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Sendspark account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Sendspark capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_dynamic_campaignREADGet one Sendspark dynamic video campaign by workspace and campaign ID.
INPUTS: workspaceId / dynamicId
add_prospectWRITEAdd a prospect to a Sendspark dynamic video campaign.
INPUTS: workspaceId / dynamicId / processAndAuthorizeCharge / prospect / prospectDepurationConfig
create_dynamic_campaignWRITECreate a Sendspark dynamic video campaign in a workspace.
INPUTS: workspaceId / name
get_prospect_by_emailREADGet Sendspark prospect data by email for a dynamic campaign, including generated video URLs when available.
INPUTS: workspaceId / dynamicId / email
list_dynamic_campaignsREADList Sendspark dynamic video campaigns in a workspace with optional pagination and search filters.
INPUTS: workspaceId / limit / offset / search / filters
INPUT CONTRACTS
Know what the action needs before it runs.
get_dynamic_campaign
workspaceIdREQUIRED- The Sendspark workspace identifier.
dynamicIdREQUIRED- The Sendspark dynamic video campaign identifier.
add_prospect
workspaceIdREQUIRED- The Sendspark workspace identifier.
dynamicIdREQUIRED- The Sendspark dynamic video campaign identifier.
processAndAuthorizeChargeREQUIRED- Whether to acknowledge and authorize charges associated with processing this prospect.
prospectREQUIRED- Prospect fields used to create a Sendspark dynamic video.
prospectDepurationConfigOPTIONAL- Duplicate handling settings used when adding a Sendspark prospect.
create_dynamic_campaign
workspaceIdREQUIRED- The Sendspark workspace identifier.
nameREQUIRED- The unique campaign name within the workspace.
get_prospect_by_email
workspaceIdREQUIRED- The Sendspark workspace identifier.
dynamicIdREQUIRED- The Sendspark dynamic video campaign identifier.
emailREQUIRED- The prospect email address to look up.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Dynamic Campaign
Get one Sendspark dynamic video campaign by workspace and campaign ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_dynamic_campaignControl Add Prospect
Add a prospect to a Sendspark dynamic video campaign. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_prospectVerify with Get Prospect By Email
Get Sendspark prospect data by email for a dynamic campaign, including generated video URLs when available. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_prospect_by_emailSAFETY BOUNDARY
Operate Sendspark with explicit limits
- Authorize Sendspark with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Sendspark rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Sendspark task completed successfully.
CONNECTION MODEL
API key
Sendspark workspace API key sent with the x-api-key header. Create or view it in the Sendspark API Credentials tab: https://sendspark.com/settings/api-credentials.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Sendspark.