Flexmail 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 Flexmail. Routes through Apideck with serviceId "flexmail".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Access Flexmail 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 Flexmail plumbing.
flexmailActivate this skill when the user explicitly wants to work with Flexmail — for example, "pull contacts in Flexmail" or "sync leads in Flexmail". This skill teaches the agent:
serviceId to pass on every call (flexmail)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, or apideck-restFor the raw OpenAPI spec:
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 Flexmail
const { data } = await apideck.crm.contacts.list({
serviceId: "flexmail",
});The Apideck CRM unified API exposes the same methods for every connector in its catalog. Switching from Flexmail to another CRM connector is a one-string change — no rewrite, no new SDK.
// Today — Flexmail
await apideck.crm.contacts.list({ serviceId: "flexmail" });
// 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 Flexmail 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.
See apideck-best-practices for Vault setup, connection lifecycle, and handling re-auth flows.
Not every CRM operation is supported by every connector. Always verify before assuming a method works:
curl 'https://unify.apideck.com/connector/connectors/flexmail' \
-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.
When an endpoint isn't covered by the CRM unified API, use Apideck's Proxy to call Flexmail directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Flexmail'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: flexmail" \
-H "x-apideck-downstream-url: <target endpoint on Flexmail>" \
-H "x-apideck-downstream-method: GET"See Flexmail's API docs for available endpoints.
Other CRM connectors that share this unified API surface (same method signatures, just change serviceId):
odoo (beta), salesforce, hubspot, pipedrive, zoho-crm, activecampaign, close, microsoft-dynamics, and 12 more.
apideck-connector-coverage — programmatic coverage checksapideck-best-practices — architecture, Vault, pagination, error handlingapideck-node — TypeScript / Node SDK patterns9e04d86
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.