Sign inStart your trial

Fellow
01Integration field card

Fellow Integration & Workflow Automation

Run Fellow on autopilot. Keep the veto.

16 actions4 triggers

Meeting notes and action items fire into connected tools before you've read them. Rills proposes each change and waits for your call.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential productivity action from Fellow arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

FELLOW · ACTION ITEM SYNC
78

Mark 9 overdue action items complete in Fellow?

9 items · assigned >7 days ago with no updates

All flagged complete by AI note summary today

Same batch pattern as last Thursday's sync

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About Fellow automation

Action items get marked complete, notes get shared to channels, and recordings get deleted while you're still in the next meeting. The ones you'd have caught are already gone.

When Fellow runs unsupervised

Productivity tools move fast, and Fellow is no exception. When automation fires without a checkpoint, the consequences show up later as confusion, missing context, or decisions nobody remembers approving.

  • action_item.completed fires and marks a task done in your project tool before you've confirmed the work actually happened.
  • ai_note.shared_to_channel posts a raw AI summary to a client-facing channel before you've checked it for accuracy.
  • Delete a meeting recording runs on a cleanup schedule and removes a recording someone still needed as a reference.
  • Archive an action item fires on a stale-item rule and buries an open commitment that was just waiting on a reply.
  • Mark an action item complete posts a status update to a connected tool before the person it was assigned to has been told.

What Rills does inside Fellow

Rills sits between the Fellow trigger and the downstream action. When an ai_note.generated event fires or an action_item.assigned lands, Rills surfaces the proposed next step so you can approve Fellow changes before they reach anyone else.

The summary still gets shared; you just see it before it goes out.

When Fellow events should and shouldn't act on their own

Not every Fellow automation carries the same risk. Some triggers follow a pattern routine enough to let through; others touch things you'll wish you'd reviewed.

  • action_item.completed: Usually safe to graduate once you've seen a dozen correct completions in a row, but flag any that close items assigned to clients.
  • ai_note.generated: Routine for internal notes; always keep a human checkpoint before anything goes to an external contact or a shared channel.
  • ai_note.shared_to_channel: Almost always needs approval. The channel is the blast radius. A wrong summary in a client Slack is harder to walk back than a missed internal note.
  • action_item.assigned: Safe to automate routing into a task tool, but the assignment message itself should wait for your review if it goes outside the team.
04. Triggers

What wakes Rills up in Fellow

When these events fire, Rills proposes the next move and waits for your call.

  • webhook

    Action Item Assigned

    Fires when an action item is assigned to a user

  • webhook

    Action Item Completed

    Fires when an action item is marked complete in Fellow

05. Actions

What Rills can do in Fellow

4 of 16 actions across reads, writes, and updates.

  1. 01

    List action items

    Retrieve action items from your Fellow meetings with optional filtering by assignee, completion status, date range, and other criteria to integrate tasks into your workflow tools. Use this to sync meeting-generated action items with your project management system, reporting tools, or automation workflows.

  2. 02

    Mark an action item complete or incomplete

    Update the completion status of an action item in Fellow, enabling you to synchronize task progress across your workflow tools without manual updates.

  3. 03

    List meeting notes

    Search and retrieve meeting notes from your Fellow workspace with optional filtering by title, attendees, date ranges, and other criteria to integrate meeting documentation into your systems.

  4. 04

    Create a webhook subscription

    Set up a webhook endpoint to receive real-time notifications from Fellow when meeting events occur, such as when notes are created or recordings finish processing.

06. FAQ

Common questions about Fellow automation

07. NEXT MOVE

Approve every Fellow change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.