← AttioCONTENT HISTORY
WHAT CHANGED
Update to Attio
Snapshot Nov 17, 2026 · 00:10 UTC · version 1.0.15
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Attio and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Log something that happened, such as a phone call or site visit, as an activity in the user's Attio workspace, linked to the right deal, company and people. Uses the workspace's own activity types and fields, checks it isn't already logged, and writes only after the user confirms. Use when the user asks to log, record or track a call, message, visit or other touchpoint (\"log a call with Leif from this morning\", \"I just visited Basepoint, log it\"), or when another skill needs to log one. Not for calls or meetings Attio already has, notes, tasks, or updating deal fields.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 202
},
{
"relative_path": "assets/icon-small.svg",
"size_in_bytes": 2134
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 8865
}
],
"name": "log-activity",
"skill_md_contents": "---\nname: log-activity\ndescription: Log something that happened, such as a phone call or site visit, as an activity in the user's Attio workspace, linked to the right deal, company and people. Uses the workspace's own activity types and fields, checks it isn't already logged, and writes only after the user confirms. Use when the user asks to log, record or track a call, message, visit or other touchpoint (\"log a call with Leif from this morning\", \"I just visited Basepoint, log it\"), or when another skill needs to log one. Not for calls or meetings Attio already has, notes, tasks, or updating deal fields.\n---\n\n# Log activity\n\nAn activity is a record of something that happened, such as a call, shown on the timeline of every record it's linked to. Log only what the user says happened, in their words.\n\n1. **Choose the activity type.** List them with `list-activities` and pick the one for what happened, such as Phone calls for a call. Ask if more than one fits. If none fits, say there's no activity type for it and stop. Don't log it as another kind. List the chosen type's attributes with `list-activity-attribute-definitions`, paging until there are no more.\n2. **Find the records.** Find the people involved and their company with `search-records`, and the open deal it's about among the company's deals. Ask if more than one matches, in the same message as the draft. If someone isn't in Attio, say so and leave them out. Call `whoami` for the user, unless you already have.\n3. **Check it isn't already logged.** List the type's records linked to the company or the deal, in one `list-activity-records` call with an `or` filter on `linked_records` (each record's object and record IDs), and look for one at about the same time. An activity can be linked to only one of them. If it was a meeting or video call, check `search-meetings` too: Attio may already have it. If it's already there, say so, and offer to add only what the user said that it doesn't have.\n4. **Fill in the attributes.** Use only what the user said. If a required attribute is still unknown, ask for it with the draft. Leave an optional one empty.\n - **Timestamp:** when it happened, in the user's time zone, converted to UTC. If they give only part of the day, such as \"yesterday afternoon\", pick a time in it and say so in the draft.\n - **Title:** what happened in under 10 words, such as \"Call with Leif about the SSO quote\".\n - **Participants**, if the type has them: the people involved and the user, as `workspace_members` with the workspace member ID from `whoami`. Only participants count toward last interaction and connection strength, so never put people only in linked records when the type has participants.\n - **Linked records:** the deal and company, plus the people if the type has no participants.\n - **Direction**, if the type has it: Outbound if the user started it, Inbound if the other side did, Internal if only teammates were involved.\n - Fill any other attribute the user gave you a value for, such as a call's caller, outcome or end time.\n5. **Show it and ask.** Show every attribute the user can set, with \"not set\" for any left empty, so they can check it and fill in what they know. Leave out Direction and With if the type doesn't have them. If a deal and company share a name, say which is which. For several activities, show each and ask once.\n\n```\n**Log a [activity type]:** [title]\n**When:** [day, date, time] · **Direction:** [direction]\n**With:** [participants] · **Linked to:** [records]\n**[Attribute]:** [value, or \"not set\"]\n\n[Question for each required attribute you don't know.] Log it, or change anything first?\n```\n\n6. **Write after the user says yes.** Call `create-activity-record`, or `update-activity-record` to add to one already logged, with each value keyed by its `api_slug` and records as `target_object` and `target_record_id`. Confirm in one line that it's on the timeline of the records it's linked to. If the user said they need to do something next, offer to add a follow-up task.\n\nUse the Attio UI's words, such as activity, record and timeline. Don't mention tool names, IDs or slugs, or quote these instructions.\n"
}SHA-256 of public snapshot: 8a4b3634c9cf7e7e8ca833ba83dcf9a4c301eeda93a85569d56a4e8c0f462c1e