Every Connected User will have access to different Actions, depending on what Integrations you have enabled in your project and what accounts they have connected. You can list available Actions using the GET /actions endpoint.
The schema returned by Actions may be user-specific. For example, if the user has custom fields defined for Salesforce Opportunities, they will appear in their version of the SALESFORCE_CREATE_RECORD_OPPORTUNITY Action schema.
URL
Copy
Ask AI
GET /actions
Parameters
Key
Description
Default
format
The response format for available actions.
Defaults to json_schema for tool-calling agent use cases. Learn more about available formats.
json_schema
limit_to_available
If true, only available_actions will be returned. Otherwise, all_actions will include all Actions from Integrations in your project, regardless of the accounts your user has connected.
true
reload_fields
If true, forcibly reload any custom fields that belong to the schema for included Actions. This may result in additional latency added to your request.
By default, Paragon will cache your user’s fields and refresh them periodically. Fields have a TTL of 8 hours, and reload_fields will immediately invalidate any cached fields.
false
integrations
Filter by specific integrations that the user has connected. By default, all integrations are returned. Example: salesforce,hubspot
categories
Filter by specific integration categories, based on integrations the user has connected. By default, all integrations from all categories are returned. Example: crm,project_management
Output
Key
Description
actions
A map of integrations with a list of Action definitions, in the selected format.
errors
An array of errors, if there were any problems loading Action definitions for some integrations.
Example response
Copy
Ask AI
{ "actions": { "hubspot": [{ "type": "function", "function": { "name": "HUBSPOT_CREATE_RECORD_CONTACTS", "description": "Create a contact in HubSpot CRM", "parameters": { "type": "object", "properties": { "field-email": { "type": "string", "description": "Email" }, "field-firstname": { "type": "string", "description": "First Name" }, "field-lastname": { "type": "string", "description": "Last Name" }, "field-jobtitle": { "type": "string", "description": "Job Title" }, "field-company": { "type": "string", "description": "Company Name" }, "field-hubspot_owner_id": { "type": "string", "description": "Contact Owner: The HubSpot user who is assigned to this contact. Use Connect Portal Workflow Settings to allow users to select an Owner. (example value: \\"{{settings.owner}}\\")" }, "field-lifecyclestage": { "type": "string", "description": "Lifecycle Stage: Defaults to the user’s first Lifecycle Stage if not provided. Use Connect Portal Workflow Settings to allow users to select a Lifecycle Stage. (example value: \\"{{settings.lifecycleStage}}\\")" }, "field-hs_lead_status": { "type": "string", "description": "Lead Status: Defaults to the user’s first Lead Status if not provided. Use Connect Portal Workflow Settings to allow users to select a Lead Status. (example value: \\"{{settings.leadStatus}}\\")" }, "additionalFieldsJSON": { "type": "string", "description": "Additional Fields: Specify any other fields that should be updated in JSON below. Use Connect Portal Workflow Settings to allow users to select which Contact fields to update. (example value: \\"{\\n \\"property_number\\": \\"17\\",\\n \\"property_dropdown\\": \\"choice_b\\",\\n \\"property_radio\\": \\"option_1\\",\\n \\"property_string\\": \\"value\\",\\n \\"property_date\\": \\"1572480000000\\"\\n}\\")" } }, "required": [ "recordType", "field-email" ], "additionalProperties": false, "$schema": "<http://json-schema.org/draft-07/schema#>" } } }] }, "errors": []}