Community skillDraft — source instructions not independently live-testedWork & collaboration

Attio for Meta Muse

Community draft proposes: Explore a community Attio draft for listing CRM objects and querying records; its upsert, note and task writes do not match Attio's API.

Guide description: The pinned helper has plausible documented routes for listing Attio objects and querying records with an appropriately scoped token. Its advertised record upsert, note and task commands send request shapes that do not meet Attio's current API requirements. OpenTools has not installed or live-tested this skill.

Community draft, not independently live-tested. An Attio workspace administrator must create an access token with the necessary read scopes. Muse custom-skill and secure credential support must also be available. The `auth` command lists one object as an access check, not proof that record queries work. Do not use the pinned upsert, note or task commands until their payloads are repaired and verified.

View original source ↗

How to set it up

Paste a prompt

Draft — these instructions come from the linked source and have not been independently live-tested by OpenTools.

Source maturity: 🧪 Draft: written from Attio's public API docs; not yet live-tested end-to-end.

Before you start

  • Attio workspace administrator-created access token with `object_configuration:read`; record queries additionally need `record_permission:read`
  • Muse custom-skill installation and secure credential support, if available to this account

Steps

  1. Review the pinned connectors/attio/SKILL.md and its Files list (SKILL.md, bin/attio.py).
  2. Have an Attio workspace administrator create an access token with `object_configuration:read` and, for record queries, `record_permission:read`. Provide it only through Muse's secure credential flow if available.
  3. Ask Muse to fetch the pinned skill and its exact listed files. Treat this as an upstream proposed installation, not a verified one-click setup.
  4. Run the source status check `bin/attio.py auth` and inspect its object-list response. It does not verify CRM queries or write actions.
  5. Do not run the pinned `upsert`, `note` or `task` commands; their request shapes conflict with Attio's current API. The source's example `query` filter is also unverified.

Prompt to paste into Muse

Inspect this community skill: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/attio/SKILL.md
Read its Files manifest. If this Muse account supports custom skill installation and secure credentials, install exactly those files; otherwise report that the setup is unavailable. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the actual result.

Account access: Bearer API key via the secure credential flow (`credentials.request_api_access`); created in Attio under Workspace settings > Developers

Allowed hosts: api.attio.com

Source status check: `bin/attio.py auth` (must return `"ok": true`)

A successful source status check may verify only configuration or credentials; it is not proof of a working end-to-end integration.

Services it connects with

These are the services the connector uses.

← Browse all Muse connectors