api-skills

Access Financials integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Access Financials. Routes through Apideck with serviceId "access-financials".

Acerta integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Acerta. Routes through Apideck with serviceId "acerta".

Act 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 Act. Routes through Apideck with serviceId "act".

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".

Acumatica integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Acumatica. Routes through Apideck with serviceId "acumatica".

ADP iHCM integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in ADP iHCM. Routes through Apideck with serviceId "adp-ihcm".

RUN Powered by ADP integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in RUN Powered by ADP. Routes through Apideck with serviceId "adp-run".

ADP Workforce Now integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in ADP Workforce Now. Routes through Apideck with serviceId "adp-workforce-now".

AFAS Software integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in AFAS Software. Routes through Apideck with serviceId "afas".

Simployer One integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Simployer One. Routes through Apideck with serviceId "alexishr".

Amazon Seller Central integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in Amazon Seller Central. Routes through Apideck with serviceId "amazon-seller-central".

Task playbook for fetching a month-end financial snapshot via the Apideck MCP server's `apideck-month-end-close-check` workflow tool. Use when the user asks for a P&L, balance sheet, aged creditors, or aged debtors view at a point in time. Read-only, idempotent, returns partial snapshots when some reports aren't supported by the connector.

Task playbook for converting a hired ATS applicant into an HRIS employee via the Apideck MCP server's `apideck-onboard-employee` workflow tool. First cross-unified-API workflow — requires both ATS and HRIS connections active on the consumer. Optionally moves the applicant to a "hired" stage in the ATS to close the loop.

Task playbook for paying a vendor bill via the Apideck MCP server's `apideck-pay-bill` workflow tool. Use when the user asks to settle, pay, or close a known accounts-payable bill in QuickBooks, Xero, NetSuite, or any other connected accounting service. Covers confirmation prompts, partial payments, payment-method capitalization quirks, and the AP-vs-AR routing decision agents routinely get wrong.

Task playbook for recording a customer payment against an invoice via the Apideck MCP server's `apideck-receive-customer-payment` workflow tool. Use when the user says a customer paid an invoice and wants the accounting service updated. AR mirror of `apideck-pay-bill` — same shape, opposite ledger side. Different unified endpoint, different counterparty (customer vs supplier), different allocation type.

Front-door skill for the Apideck MCP server — 330 unified-API tools across 10 domains plus 4 intent-grouped workflow tools, exposed via dynamic discovery. Use when the user is building an MCP-based agent (Claude Code, OpenAI Agents SDK, Pydantic AI, LangChain) and wants to integrate with any of the 200+ SaaS connectors Apideck covers. Hosted at mcp.apideck.dev/mcp; stdio transport via `npx -y @apideck/mcp` for local development.

Apideck Unified API — one set of methods for 146+ SaaS connectors across CRM (21 connectors), Accounting (34), HRIS (58), ATS (11), File Storage (5), Issue Tracking (6), and Ecommerce (17). Route to Salesforce, HubSpot, QuickBooks, Xero, NetSuite, BambooHR, Workday, Greenhouse, SharePoint, Google Drive, Jira, Shopify, and 130+ more by changing a single serviceId string. Use as the starting point whenever the user wants to integrate with a SaaS app — check Apideck coverage first, then use a connector-specific skill (e.g. `salesforce`, `hubspot`) or the language SDK skill (`apideck-node`, `apideck-python`, etc.).

Asana via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Asana's native API. Use when the user wants to call Asana (no unified API resource mapping). Routes through Apideck with serviceId "asana".

Attio 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 Attio. Routes through Apideck with serviceId "attio".

Microsoft Entra integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Microsoft Entra. Routes through Apideck with serviceId "azure-active-directory".

Azure DevOps via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Azure DevOps's native API. Use when the user wants to call Azure DevOps (no unified API resource mapping). Routes through Apideck with serviceId "azure-devops".

BambooHR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in BambooHR. Routes through Apideck with serviceId "bamboohr".

banqUP integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in banqUP. Routes through Apideck with serviceId "banqup".

Basecamp via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Basecamp's native API. Use when the user wants to call Basecamp (no unified API resource mapping). Routes through Apideck with serviceId "basecamp".

BigCommerce integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in BigCommerce. Routes through Apideck with serviceId "bigcommerce".

Blackbaud 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 Blackbaud. Routes through Apideck with serviceId "blackbaud".

bol.com integration via Apideck's Ecommerce unified API — same methods work across every connector in Ecommerce, switch by changing `serviceId`. Use when the user wants to read, write, or sync orders, products, customers, and stores in bol.com. Routes through Apideck with serviceId "bol-com".

Box integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in Box. Routes through Apideck with serviceId "box".

Breathe HR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Breathe HR. Routes through Apideck with serviceId "breathehr".

Bullhorn ATS integration via Apideck's ATS unified API — same methods work across every connector in ATS, switch by changing `serviceId`. Use when the user wants to read, write, or sync jobs, applicants, and applications in Bullhorn ATS. Routes through Apideck with serviceId "bullhorn-ats".

Campfire integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Campfire. Routes through Apideck with serviceId "campfire".

IRIS Cascade HR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in IRIS Cascade HR. Routes through Apideck with serviceId "cascade-hr".

CatalystOne integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in CatalystOne. Routes through Apideck with serviceId "catalystone".

Cegid Talentsoft integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Cegid Talentsoft. Routes through Apideck with serviceId "cegid-talentsoft".

Ceridian Dayforce integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Ceridian Dayforce. Routes through Apideck with serviceId "ceridian-dayforce".

Cezanne HR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in Cezanne HR. Routes through Apideck with serviceId "cezannehr".

CharlieHR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in CharlieHR. Routes through Apideck with serviceId "charliehr".

CIPHR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in CIPHR. Routes through Apideck with serviceId "ciphr".

Clear Books integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Clear Books. Routes through Apideck with serviceId "clearbooks-uk".

ClickUp via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to ClickUp's native API. Use when the user wants to call ClickUp (no unified API resource mapping). Routes through Apideck with serviceId "clickup".