Home
Menu

Connections

Send notes to your calendar, save ideas as files, and run actions in your other tools

The Connections page links smiet to the tools you already use. There are two kinds of connection:

  • Calendar and tasks (CalDAV): your own calendar server, for tasks, events and idea notes.
  • Services: tools like Linear, Todoist, Notion or SeggWat. smiet talks to them over MCP and can run their actions for you, like creating an issue.

smiet never runs an action in a service without your confirmation. The only automatic sending is to your calendar server and idea folder, and only if you turn it on.

The Where notes go card shows who carries out each kind of note: your calendar server, your iPhone, a connected service, or your AI assistant. It follows your settings on this page and whether the smiet iPhone app synced in the last 14 days, so there is nothing to set there.

Send tasks and events to your calendar

smiet can add Task notes as to-dos and Event notes as calendar entries on your own CalDAV server, for example Nextcloud, iCloud, Fastmail or Radicale.

1

Create an app password

Create an app password on your calendar server. In Nextcloud, go to Settings → Security → Devices & sessions → Create new app password.

2

Connect

In Connections, under Calendar and tasks (CalDAV), enter the Server URL, your Username and the App password, then choose Connect. The server's address is enough; smiet finds your calendars itself. The server must be reachable over public HTTPS.

3

Pick your calendars

Choose where Tasks go to and where Events go to, then choose Save.

Now a Task or Event note's page shows Add to tasks or Add to calendar. Press it to send the note right away.

To send new notes without a click, turn on Add tasks automatically once sorted or Add events automatically once sorted. This covers tasks that don't name a project, and events that have a start time.

What gets sent:

  • A task becomes a to-do with its due date and priority.
  • An event becomes a calendar entry with start, end and location. An event without an end lasts one hour. An event with a date but no time lasts all day.

Once a note is sent, it counts as done and moves to the Archive. Sending the same note twice never creates a duplicate.

Save ideas as notes

Ideas go to takes a WebDAV folder on the same account. Each Idea note becomes one Markdown file with its tags in the frontmatter.

  1. Find the folder's WebDAV address. In Nextcloud, open Files → Settings (bottom left), copy the WebDAV address, and add the folder name, for example https://cloud.example.com/remote.php/dav/files/USERNAME/Notes/. The folder must already exist.
  2. Paste it into Ideas go to and choose Save.
  3. On an Idea note's page, choose Save as note. Or turn on Save ideas automatically once sorted.

Connect a service

1

Pick the service

In Connections, under Services, pick one from Service: Linear, Notion, Todoist, ClickUp, Atlassian (Jira, Confluence), GitHub, monday.com or SeggWat. This fills in the name, the address and the sign-in method.

For any other service, keep Custom, enter a Name, and paste the service's MCP server URL.

Optionally add a Purpose: one line on what you use the service for, like "Work project board. Tasks for my day job." smiet reads it when several services could take a note. You can change it later on the connection.

2

Sign in or paste a token

With Sign in with the service, choose Sign in and approve access on the service's page. You come back to smiet with the connection saved.

With Access token or no authentication, paste the token and choose Connect. Leave the token empty for a public server. GitHub and monday.com need a personal access token.

3

Test it

Choose Test on the connection. It checks access, lists available actions, and tries to load all projects. It reports limitations separately. This check does not send a note or prove that a write will succeed.

Sign-ins renew themselves when the service allows it. If access expires or you revoke it, choose Reconnect. Your connection and history stay.

Disconnect removes the connection from smiet. To revoke the access itself, use the service's own settings.

SeggWat

Pick SeggWat and sign in with the service. Or choose Access token or no authentication and paste an Organization Access Token from SeggWat's Settings → API Tokens. Paste only the token, without Bearer .

To send feedback there, make it a destination of its own (next section) with the label Feedback and the action create_feedback.

Make a service its own destination

Notes go to one of four destinations: task, event, reply or idea. A connected service can add one more, like your feedback tool as Feedback.

  1. On the connection, turn on Use as its own destination.
  2. Enter a short label, up to 32 characters. It can't be Task, Event, Reply, Idea or External.
  3. Pick the action that receives the notes, then choose Save.

The label then shows as a destination in your inbox and on each note, and smiet can sort notes there. When sorting, smiet reads the service's Purpose and the action's fields to decide what belongs there. A report of something, like "a customer said X", goes to a matching destination unless you ask for work. Then it's a task.

Turn Use as its own destination off, or disconnect the service, and its open notes are sorted again.

Let smiet suggest the next step

Once a service is connected, open it from Connections. Projects lists the projects smiet found in that service. For services with supported project discovery and creation actions, smiet uses these names when sorting. If your note names a project that exists in a service, smiet matches it. Choose Refresh after you add projects or change a service.

Linear and SeggWat fit this project-based flow. Linear suggestions create new issues; updating an existing issue is a separate manual action. Todoist projects can be listed, but its task batches are not yet supported for automatic routing. Notion, ClickUp, Atlassian, GitHub and monday.com currently require you to choose the destination fields through Actions; connecting them does not enable automatic routing.

Some examples:

  • With SeggWat set up as Feedback, "Got feedback for Highlander that it looks good" goes to Feedback and suggests creating feedback in SeggWat's Highlander project.
  • "Fix Highlander's login bug by Friday" suggests creating an issue in your board's Highlander project.
  • "A customer reported broken login in Highlander" goes to Feedback too. Without such a destination it becomes an idea. If you ask to investigate it, it becomes a task.

On the note's page, Suggested next step shows the result: the destination, the project, a short explanation, and the words from your note it was based on. Why this suggestion? says in plain words what the analysis concluded.

To send the suggestion:

  1. Choose Review and send. To change something first, choose Edit fields, then Review action.
  2. Check what will be sent, then choose Confirm and send. Choose Edit to go back.
  3. When it succeeds, the note counts as done and moves to the Archive. The service's response is saved in Action history.

If the note changed after it was sorted, you'll see a hint to re-analyze it. Refresh suggestion runs the analysis again. It can change the destination or split the note. The new suggestion is sent by itself only under the same rules as after sorting: the action is set to Always allow, or smiet is sure and you made no choice (see Choose what each action may do). If an action is already prepared, send it or choose Edit first.

A suggestion can also end without an action:

  • Needs a choice: smiet found a matching project but couldn't settle on one action, for example because two services offer it. Pick one yourself under Actions.
  • No matching action: no connected service fits this note.
  • Personal todo — nothing to send: a personal task with no project. It stays in your inbox, unless you set a personal list.

Personal list

Personal list (optional), under a connection's Projects, picks one of its projects for personal tasks that don't name one. Without it, they stay in your inbox as to-dos. There is one personal list. Choosing a project in another connection replaces it, and None removes it. Where notes go on the Connections page shows the current one.

Project nicknames

Project nicknames (optional) is for projects you call by another name, like "HL" for Highlander. It shows on the page of a service that takes feedback, such as SeggWat. Choose Add a nickname, pick the project, enter the Name in your notes, and choose Save nickname.

Choose what each action may do

Open Actions under a service to see what it offers. Each action has a setting:

  • Always allow: runs without asking. A suggested next step with this action goes out right after the note is sorted, and your AI assistant can call it directly. A note you didn't write yourself, like text shared from another app or a note your AI assistant added, always waits for you to confirm.
  • Ask first: you confirm each time. A suggested step waits for Confirm and send; an assistant has to ask you before calling it.
  • Blocked: never runs, neither from automatic sorting nor from an assistant.

Without a choice, actions that only read (like list_issues) run. The rest ask first, with one exception: a suggested next step goes out right after the note is sorted when smiet is sure about what the note is, where it goes and what it says. The note's activity then shows "Sure enough to send without asking". This never happens for a note you didn't write yourself. An assistant still has to ask. Choose Ask first to confirm every time.

When a service changes an action's fields, or adds an action after you connected it, smiet holds it, marked Changed or New, until you choose Accept. Until then it doesn't run. smiet checks this each time it asks the service for its actions.

Run an action by hand

  1. Open a note and scroll to Actions.
  2. Choose a Connection, then an Action from that service's list.
  3. Fill in the fields. smiet fills in what it can from the note; check it. For complex fields, turn on Edit as JSON.
  4. Choose Review action, then Run action.
  5. Read the result in Action history.

An action you run by hand doesn't mark the note as done, because a lookup like list_projects doesn't finish anything. Press Done when the work is complete.

When the outcome is unknown

Outcome unknown means the action may have run, but smiet got no final answer. Check the service before you try again. Refresh reloads the saved result without sending anything.

Once you've checked, open Resolve unknown outcome:

  1. Under What happened in the service?, choose The item was created or No item was created.
  2. Add the item's ID or link, or what you checked.
  3. Confirm that the original request is no longer running, and choose Record checked outcome.

Recording doesn't send the action again. If you record that the item was created, a suggested action counts as done. If nothing was created, you can prepare a new one.

What works

  • Services must be remote MCP servers at a public HTTPS address. Local programs and servers on a private network don't work.
  • Sign-in works with services that support standard OAuth sign-in with PKCE. Services that need you to register an OAuth app by hand aren't supported yet. Use a token instead, if the service offers one.
  • A sign-in has to finish in the same browser within ten minutes.
  • To discover projects, the service needs a recognized listing action such as list_projects or find-projects with no required arguments. Cursor pagination is supported up to 10 pages and 500 projects. An incomplete list is reported instead of used for matching. Other services can be used through Actions, subject to their required fields and permissions.
  • Sorting sees project names, aliases and the services' action descriptions. It doesn't see your tokens or other content from the service.