Activecampaign
One abstraction, 146 SaaS connectors. Agent skills for Apideck's Unified API — integrate Salesforce, QuickBooks, BambooHR, Jira, Shopify and 140+ more by changing one string.
npx -y skills add apideck-libraries/api-skills --skill activecampaignAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
ActiveCampaign integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in ActiveCampaign. Routes through Apideck with serviceId "activecampaign".
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
5.8 KB, as published. Nobody here has run it
ActiveCampaign (via Apideck)
Access ActiveCampaign through Apideck's CRM unified API — one of 21 CRM connectors that share the same method surface. Code you write here ports to Odoo, Salesforce, HubSpot and 17 other CRM connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant ActiveCampaign plumbing.
Quick facts
- Apideck serviceId:
activecampaign - Unified API: CRM
- Auth type: apiKey
- Gotchas: page
- ActiveCampaign docs: https://developers.activecampaign.com
- Homepage: https://www.activecampaign.com/
When to use this skill
Activate this skill when the user explicitly wants to work with ActiveCampaign — for example, "pull contacts in ActiveCampaign" or "sync leads in ActiveCampaign". This skill teaches the agent:
- Which Apideck unified API covers ActiveCampaign (CRM)
- The correct
serviceIdto pass on every call (activecampaign) - ActiveCampaign-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node,apideck-python,apideck-dotnet,apideck-java,apideck-go,apideck-php, orapideck-rest
For the raw OpenAPI spec:
Minimal example (TypeScript)
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List contacts in ActiveCampaign
const { data } = await apideck.crm.contacts.list({
serviceId: "activecampaign",
});
Portable across 21 CRM connectors
The Apideck CRM unified API exposes the same methods for every connector in its catalog. Switching from ActiveCampaign to another CRM connector is a one-string change — no rewrite, no new SDK.
// Today — ActiveCampaign
await apideck.crm.contacts.list({ serviceId: "activecampaign" });
// Tomorrow — same code, different connector
await apideck.crm.contacts.list({ serviceId: "odoo" });
await apideck.crm.contacts.list({ serviceId: "salesforce" });
This is the compounding advantage of using Apideck over integrating ActiveCampaign directly: code against the unified CRM API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Authentication
- Type: API Key
- Managed by: Apideck Vault — the user pastes their ActiveCampaign API key into the Vault modal; Apideck stores it encrypted and injects it on every request.
- Rotation: if the user rotates their key, they re-enter it in Vault. No code changes needed.
See apideck-best-practices for Vault setup, connection lifecycle, and handling re-auth flows.
Verifying coverage
Not every CRM operation is supported by every connector. Always verify before assuming a method works:
curl 'https://unify.apideck.com/connector/connectors/activecampaign' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}"
See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.
Escape hatch: Proxy API
When an endpoint isn't covered by the CRM unified API, use Apideck's Proxy to call ActiveCampaign directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on ActiveCampaign's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: activecampaign" \
-H "x-apideck-downstream-url: <target endpoint on ActiveCampaign>" \
-H "x-apideck-downstream-method: GET"
See ActiveCampaign's API docs for available endpoints.
Sibling connectors
Other CRM connectors that share this unified API surface (same method signatures, just change serviceId):
odoo (beta), salesforce, hubspot, pipedrive, zoho-crm, close, microsoft-dynamics, teamleader, and 12 more.
See also
- CRM OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- ActiveCampaign official docs