Agent Skill · Paragon

paragon-actionkit-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

View SKILL.md on GitHub → Source repository Provider profile

Provider: Paragon Path in repo: skills/experimental_actionkit-skill/SKILL.md

Skill body

When to use this skill

Use this Skill to help the user implement ActionKit API calls in their code, by using the references in the Table of Contents

ActionKit Overview

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.

Some examples of ActionKit Tools are:

NOTION_CREATE_PAGE
SALESFORCE_UPDATE_RECORD
SLACK_SEND_DIRECT_MESSAGE

Some examples of Action Triggers are:

NOTION_PAGE_CREATED
SALESFORCE_RECORD_CREATED
SLACK_MESSAGE_RECEIVED

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

Prerequisites

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

Tools API

If the user needs to list Tools: List Tools docs
If the user need to execute run Tool: Run Tools docs
If the user mentions that they would like to use a 3rd-party API that ActionKit does not currently have a pre-built action for: Use Proxy API

Triggers API

If the user needs to list Triggers: List Triggers docs
If the user needs to subscribe to a Trigger: Subscribe to Trigger docs
If the user needs to see example payload for a Trigger: Example Trigger payload docs
How to receive Trigger webhooks can be found: Receiving Webhooks docs
Other useful endpoints such as listing subscribed Triggers, updating a Trigger, and unsubscribing to a Trigger can be found crawling the Triggers Overview