PostHog API
Arcade Unoptimized
Tools that enable LLMs to interact directly with the PostHog API.
Author:Arcade
Version:
0.2.1Auth:No authentication required
766tools
766require secrets
Arcade Toolkit provides developers with the tools to interact seamlessly with the PostHog API, enhancing their ability to manage projects efficiently. The toolkit allows for various API operations such as adding collaborators, managing dashboards, and executing saved queries.
Capabilities:
- Supports managing and updating dashboards and their settings.
- Facilitates the addition of collaborators for effective project collaboration.
- Enables querying and manipulating project data through saved queries and insights.
- Manages environment-specific settings and configurations for enhanced project organization.
- Tracks insights activity and user engagements to better analyze project performance.
OAuth: There is no OAuth authentication type required for access.
Secrets:
- API keys and tokens managed securely.
- Example secrets include POSTHOG_SERVER_URL and POSTHOG_PERSONAL_API_KEY.
Available tools(766)
766 of 766 tools
| Tool name | Description | Secrets | |
|---|---|---|---|
Add a collaborator to a specific dashboard.
Use this tool to add a collaborator to a specified dashboard within a project environment on Datadog.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Create a new data color theme for a project.
Use this tool to create a new data color theme within a specified project on Datadog. This is useful when you need to apply customized color visualizations to data within a project.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Create or update persons in a funnel correlation.
This tool is used to handle persons within a funnel correlation context, specifically for reading and deleting purposes. For creating or updating persons, consider using the capture API or relevant SDKs.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path, query parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path, query parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Add persons to a static cohort in Datadog.
This tool updates a static cohort by adding new persons to it in a specified project within Datadog. | 2 | ||
Add a session recording to a specified playlist.
This tool allows you to add a session recording to a specific playlist within a project. It should be called when you need to track or log a session recording view in a particular playlist.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Create a warehouse saved query for data management.
Use this tool to create a new saved query for warehouse data management within a specified project. It helps in managing warehouse tables effectively.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Create a new warehouse table in a specified project.
Use this tool to create a new warehouse table within a specified project using its project ID. Useful for initializing data structures in a warehouse environment.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Append log entries to a specific task run log array.
This tool is used to add one or more log entries to the log array of a specified task run, identified by project, task, and run IDs.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Cancel a batch export backfill process.
Use this tool to cancel an ongoing batch export backfill for a specific project and batch. It should be called when a backfill process needs to be halted.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Cancel an ongoing batch export run.
Use this tool to cancel an ongoing batch export run in DataDog. It should be called when you need to stop a specific export process immediately.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Cancel a pending email change request.
Use this tool to cancel a pending email change request for a user in the system. It ensures that the email update process is stopped.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 2 | ||
Cancel the creation of an environment insight.
Use this tool to cancel an ongoing creation process for an environment insight in Datadog.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path, query parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path, query parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Cancels an invitation to join an organization.
This tool is used to cancel an invitation for someone to join an organization in Datadog. It should be called when you need to revoke an invite that has already been sent. | 2 | ||
Cancel a running saved query workflow in progress.
Use this tool to cancel an ongoing saved query execution within a project. Useful when you need to stop a query that is currently running to avoid unnecessary resource usage.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Cancel a running saved query workflow in Datadog.
This tool cancels a running saved query workflow based on the provided project and query IDs. It should be called when you need to stop an ongoing query execution in Datadog's environment warehouse.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Checks authorization for creating asynchronous queries.
Call this tool to determine if a user is authorized to create asynchronous queries in a specific Datadog project. Useful for workflows that need to verify permissions before proceeding with query operations. | 2 | ||
Check if demo data is being generated for a project.
Use this tool to determine whether demo data is currently being generated for a specific project within an organization. | 2 | ||
Check authentication for Datadog environment asynchronously.
This tool checks if a user has authentication permissions for a specific Datadog environment asynchronously. It should be called when there is a need to verify user access permissions for a given project. | 2 | ||
Check if a property has been seen with specified event names.
This tool checks whether a specified property has ever been associated with a list of given event names. It returns a mapping of each event name to a boolean, indicating whether the association exists. Useful for analyzing event-property relationships in a project. | 2 | ||
Mark a project's product onboarding as complete in an organization.
Use this tool to update and complete the product onboarding process for a specific project within the current organization. It is applicable when an onboarding process needs to be marked as finished.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Complete the uploading process for symbol sets in error tracking.
Use this tool to finalize the upload process for symbol sets in error tracking environments. Typically called after all parts of symbol sets are uploaded to signal completion. | 2 | ||
Finalize the upload of symbol sets in Datadog error tracking.
Use this tool to complete the upload process of symbol sets in Datadog's error tracking environment for a specific project. Call this when you need to finalize an upload that has already started. | 2 | ||
Get count of all files in a specified folder.
Use this tool to obtain the total number of files within a specific folder in a given project environment.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Create a new annotation for a project.
Use this tool to create a new annotation within a specified project in Datadog. This can be used to track important events or notes related to project data.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 | ||
Create a new backfill for a BatchExport.
This tool is used to create a new backfill for a BatchExport by specifying the project and batch export IDs. It should be called when there's a need to initiate a backfill operation for specific data exports.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 |
Page 1 of 31(25 of 766)
Last updated on