Tool groups
An automation’s reach is set by tool groups, shown as “What it can look at” and “What it can change” on the automation’s Configuration tab. A tool is available to a scheduled run only if the automation’s allowlist includes its group. The groups that deliver work:
A connected plugin, such as Notion, is its own group named after the plugin.
If a scheduled run needs an integration that the automation’s tool list does not include, nothing is added to your Inbox, because connecting it would not help that run. It is recorded on the run’s transcript instead. To fix it, add the tool’s group to the automation.
Reading the web
web_fetch reads one page. find_contact reads the pages of a site to find who runs it. Both, and the refresh of your site’s page map, go through our web reader.
- Each open-web read is metered in credits. See Credits.
web_fetchreads Reddit threads free of charge, and returns the post, the top comments, whether the thread still takes replies, and the subreddit’s rules.- When the web reader is unavailable, reads fall back to a plain HTTP fetch with no JavaScript rendering. Pages built entirely in JavaScript may come back empty then, and the agent says so instead of guessing what the page says.
find_community_threads lists the community threads (Reddit, Hacker News, Stack Overflow and Stack Exchange, Quora) that answers to your tracked prompts cite. It is free and read-only. See Community answers.
Pull requests
resolve_url_to_file finds the file behind a URL in your connected repositories. It also reports where the page’s title and description are defined, and where a new page at that URL would go.
propose_fix proposes a change to a file as a pull request (see GitHub).
- Proposing a path that does not exist creates a new file, such as a new post under a content root.
prompt_ids(optional) names the tracked prompts the change is meant to move. Those are the prompts re-read after it ships. Without them no before-and-after is measured.
Articles and posts
write_document writes an article. It also appears as a work item under Work → To approve and as a draft on the content plan. Where it goes on approval depends on what is connected:
- A connected GitHub repository with a blog directory: approving opens a pull request that adds the post as a new file, with front matter that follows your existing posts.
- A mapped Notion blog: approving sends it to Notion as a draft page.
- Otherwise, a copy handoff: you paste it into your site and mark it shipped with the live URL.
draft_social_post leaves a LinkedIn post in Work, ready to copy. Attensira never posts to LinkedIn: you post it from your own account and mark it shipped with the post’s link. The post always carries the link to its source page.
Notion posts
list_blog_posts and read_blog_post list and read the posts in your mapped Notion blog. propose_blog_update proposes a new version of one as a before/after. All three are offered only when a Notion blog database is mapped. See Notion blog.
Client reports
publish_client_report publishes the client report for the period that just ended. It runs only when the automation’s allowlist includes Publish the client report. The agent writes only the words (summary, highlights, next period, notes); every number on the report is read from the workspace’s data for the closed period.