Terminal
Terminal/Skill
Skill for using Paragon's ActionKit API for 3rd-party Tools and Triggers, Tools for CRUD-like operations in a 3rd-party API and Triggers for subscribing to 3rd-party webhooks
By Paragon
Works with
npx skills add useparagon/paragon-ai-skills --skill paragon-actionkit-skillUse this Skill to help the user implement ActionKit API calls in their code, by using the references in the Table of Contents
ActionKit exposes thousands of pre-built Tools (actions in a third-party system) and Triggers (events in a third-party system) across integrations through one consistent interface.
When explaining the API, prefer the current Tools terminology and /tools endpoints. Older /actions naming still works for backward compatibility, but the docs now position /tools as the primary interface.
ActionKit Tool schemas support multiple formats depending on the user's implementation:
format=json_schema (default) for AI agent tool calling and other programmatic use casesformat=paragon for rendering configurable UI inputs in workflow builders or other frontend configuration experiencesFor polymorphic Tools, the json_schema format may split a generic Tool into more specific Tool names, while the paragon format keeps the generic Tool and represents branching inputs inside the schema.
Some examples of ActionKit Tools are:
NOTION_CREATE_PAGESALESFORCE_UPDATE_RECORDSLACK_SEND_DIRECT_MESSAGESome examples of Action Triggers are:
NOTION_TRIGGER_PAGE_CREATEDSALESFORCE_TRIGGER_RECORD_CREATEDSLACK_TRIGGER_MESSAGE_RECEIVEDThe full list of available Tools and Triggers can be found in the ActionKit docs
Popular use cases for ActionKit include
AI agent tool calling: Expose all actions as function tools to your AI agent over the API or MCP server, with agent-optimized descriptions for tool calling accuracy.
Front-end functions: For use cases where your users interact with integration data in your app, like displaying a table of Salesforce opportunities or a button to send a Slack notification.
Integrations for your workflow product: Expose all actions as integration nodes in your workflow automation product/feature by wrapping ActionKit’s input schemas.
ActionKit is built on top of Paragon's managed authentication and monitoring. When using ActionKit, a JWT with a unique end-user ID is required so that Paragon knows who the action should be run on behalf of.
Before helping the user implement ActionKit, it's best to have the Paragon SDK and Connect Portal setup.
Check the user's project for "@useparagon/connect" in their package.json or references of paragon.authenticate in their frontend codebase
If a user does not have the Paragon SDK and Connect Portal for authorization set up: Direct them to use the paragon-setup-skill
If the user does have the Paragon SDK and authorization set up: Proceed with using the resources in the "Table of Contents" to help implement ActionKit
list Tools: List Tools docsformat=json_schema (the default) when listing Toolsformat=paragon when listing Toolsrun Tool: Run Tools docslist Triggers: List Triggers docssubscribe to a Trigger: Subscribe to Trigger docsexample payload for a Trigger: Example Trigger payload docslisting subscribed Triggers, updating a Trigger, and unsubscribing to a Trigger can be found crawling the Triggers Overview