Question 1

What manual work can be automated when using Fellow?

Accepted Answer

Manual tasks around Fellow that can be automated include distributing meeting summaries to specific team members or channels, logging summary data into CRM or project management tools, creating follow-up tasks from action items Fellow identifies, and triggering notifications when specific keywords or decisions appear in transcripts. Automation can also route summaries to different destinations based on meeting type or attendee list, eliminating the need to manually send or copy summaries after each meeting.

Question 2

How does data flow between Fellow and other business tools?

Accepted Answer

Fellow meeting summaries and transcripts can be sent to downstream tools via API or webhook integrations, allowing data like action items, decisions, and attendee lists to populate records in connected systems. Data typically flows out of Fellow after a meeting is recorded and processed, then triggers actions in other tools such as creating tasks, updating project records, or sending notifications. The timing and structure of data sent depends on how the integration is configured, but Fellow provides the summary content in a structured format that can be mapped to fields in destination systems.

Question 3

What are common issues when automating workflows with Fellow?

Accepted Answer

Fellow's summaries and transcripts depend on audio quality and clear speech recognition, so poor meeting audio can result in incomplete or inaccurate data being passed to other systems. Timing mismatches can occur if automations attempt to access a summary before Fellow has finished processing the recording, causing workflows to fail or repeat. Privacy and access controls matter: automations must respect user permissions and data retention settings, as Fellow prioritizes security and may limit which summaries can be exported or who can access them through integrations.

Question 4

How should we set up Fellow so automations run reliably?

Accepted Answer

Ensure Fellow is configured with consistent meeting recording settings across teams, as automations depend on uniform data structure and timing. Establish clear naming conventions or labels for meetings that automations can use to route summaries to the correct destinations or trigger specific workflows. Test integrations with a small set of meetings first to confirm summaries are being captured and exported correctly before rolling out automation to all meetings, and maintain a record of which automations depend on which meeting types or data fields so changes can be coordinated.

Automate the manual work in Fellow

Fellow by the numbers

Top 5 Fellow friction points when done manually

Meeting notes scattered across Fellow

Fellow action items never assigned clearly

Manually copying Fellow notes to task lists

Fellow decisions get lost between meetings

Following up on Fellow action items manually

What you can automate in Fellow

Add new rows in Smartsheet when action items are assigned to you in Fellow

Complete Fellow action items when new tasks are completed in Google Tasks

Craft new Airtable records each time notes are sent to zapier from Fellow

Create Google tasks from new Fellow action items assigned to me

Create new Sunsama tasks when action items are assigned to you in Fellow

Create tasks in Motion for new action items assigned to you in Fellow

Tools commonly connected to Fellow

Fellow Automation questions

Ready to automate your work in Fellow?