ablefy MCP integration for AI agents.
Connect AI agents to ablefy through 5 structured actions, including get account, get pricing plan, and get product. Review authentication, inputs, workflows…
- 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 ablefy integration exposes
The ablefy Agent App exposes 5 provider-backed actions for marketing and productivity work. Its current contract lets an authorized agent get the ablefy account associated with the configured api credentials, get one ablefy pricing plan by its numeric identifier, and get an ablefy product and its related pricing and author information. 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 ablefy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ablefy capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADGet the ablefy account associated with the configured API credentials.
get_pricing_planREADGet one ablefy pricing plan by its numeric identifier.
INPUTS: id
get_productREADGet an ablefy product and its related pricing and author information.
INPUTS: id
list_pricing_plansREADList pricing plans available in the connected ablefy account.
list_productsREADList products available in the connected ablefy account.
INPUT CONTRACTS
Know what the action needs before it runs.
get_pricing_plan
idOPTIONAL- The numeric ablefy pricing plan identifier.
get_product
idOPTIONAL- The numeric ablefy product identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Get the ablefy account associated with the configured API credentials. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountVerify with Get Pricing Plan
Get one ablefy pricing plan by its numeric identifier. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_pricing_planSAFETY BOUNDARY
Operate ablefy with explicit limits
- Authorize ablefy with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ablefy data may still be sensitive and should be minimized before it enters model context.
- 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 ablefy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ablefy task completed successfully.
CONNECTION MODEL
API key
ablefy API key sent as the key query parameter. Generate it under Settings > Integrations > ablefyAPI in your ablefy account: https://app.ablefy.io/.
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
- 5
- WRITE SIGNALS
- 0
- 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 ablefy.