Send authenticated HTTP requests to configured analytics provider APIs when standard actions cannot express the endpoint, filters, request body, or pagination you need. Inspect provider documentation, retrieve matching records, and report the request details and coverage gaps.
Make arbitrary authenticated HTTP calls to configured Analytics provider APIs when first-class actions are too narrow.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use provider-specific actions for common jobs, but treat them as shortcuts, not limits. When a first-class action cannot express the endpoint, filters, request body, pagination mode, or API version needed, use:
provider-api-catalog to inspect provider base URL, auth style, docs/spec
URLs, placeholders, examples, and reusable corpusRecipes.provider-api-docs to fetch registered provider docs/spec URLs.provider-api-request to make the exact HTTP call. Credentials are injected
server-side, private/internal URLs are blocked, and secrets are redacted.Clay is a credentialed GTM provider capability, not a messaging channel. Use
provider clay; the server injects CLAY_PUBLIC_API_KEY with the official
clay-api-key header and restricts requests to the exact
https://api.clay.com origin, with /public/v0 as the default base path. Use
provider-api-docs for the registered official docs and OpenAPI spec on
developers.clay.com.
Clay searches are stateful company/people iterators, routines are asynchronous, and table queries are read-only, Enterprise-only, and require a known table id. The optional local Clay CLI/MCP browser login is separate from hosted Agent Native credentials. Do not install or vendor that plugin by default; its public repository currently declares no license.
Examples:
pnpm action provider-api-catalog --provider=hubspot
pnpm action provider-api-request --provider=hubspot --method=POST --path=/crm/v3/objects/deals/search --body='{"filterGroups":[{"filters":[{"propertyName":"products","operator":"CONTAINS_TOKEN","value":"Publish"}]}],"properties":["dealname","products","dealstage","closedate"],"limit":100}'
pnpm action provider-api-request --provider=bigquery --method=GET --path=/projects/{projectId}/datasets
Always cite provider, method, path, status, filters, row/sample count, and pagination/coverage gaps in analytical answers.
For source-record body searches across transcripts, messages, tickets, issues, notes, documents, or conversation logs, use the raw body endpoint or native provider search endpoint for that record type. Parent/container metadata such as call lists, titles, summaries, or briefs is discovery evidence only; it cannot support a "no mentions" or complete body-text claim.
Example corpus recipe:
pnpm action provider-corpus-job --operation=start --mode=batch-search --request='{"provider":"gong","method":"POST","path":"/calls/transcript","body":{"filter":{"callIds":[]}}}' --batch='{"inputDatasetId":"<staged-call-id-dataset>","inputValuePath":"id","batchSize":20,"itemBodyPath":"filter.callIds","responseItemsPath":"callTranscripts"}' --search='{"queries":["Figma MCP","model context protocol"],"textPaths":["transcript"],"idPaths":["callId"]}'
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate, refine, export, and place brand images or videos from an Assets library into another app. The skill covers choosing a library, handling image batches and video runs, and updating selected assets after feedback.
Prepare a customer account health, renewal, or contract usage readout. Verify the account identity, use approved metric definitions, compare contracted capacity with actual usage, and trace findings to sources, time windows, and known gaps.
Create focused app actions that agents can call as tools and frontend code can use through client hooks. Use them to add provider integrations or fetch UI data, with validated inputs and structured results.
Use this checklist when adding a feature or integration to an agent-native app. It covers the user interface, agent-callable actions, instructions, and app-state sync so both the user and agent can work with the capability consistently.
Investigate complex questions by combining data from multiple sources, then summarize patterns, metrics, and evidence in a clear report. Save requested analyses as dashboards with instructions for future refreshes.
Use the Analytics admin surfaces to inspect and change workspace feature flags, review dashboard ownership and usage activity, or browse and edit databases connected from other agent-native apps. The skill guides administrators to the relevant view and actions.