TIL Fellow can integrate with Jira, but it's one-way. Anyone make it bi-directional?

elena_g · 2026-07-29T08:20:58Z

Hey everyone! 👋 So I was deep in my quarterly workflow review (you know how I love a good side-by-side comparison!) and finally got around to testing the Fellow Jira integration. The promise of syncing meeting action items directly to Jira tickets is fantastic for us in the product/marketing sync world. However, I quickly hit a wall: the sync is **only one-way** (Fellow → Jira). You can create a Jira issue from a Fellow action item, which is great, but any updates or comments *in Jira* don’t flow back into Fellow. This breaks the loop for us, as our engineers live in Jira and mark things done or add blockers there. My Fellow action items then become outdated, which defeats the purpose of a single source of truth! Here’s my current setup and what I’ve tried: * **Integration:** Using the native Fellow app connection in Slack, which pushes to Jira Cloud. * **Goal:** A bi-directional sync where status changes (e.g., "Done" in Jira) reflect in Fellow (e.g., checked off). * **My attempted workarounds:** * Looked into Zapier/Make: They can trigger *from* Jira, but Fellow's API doesn't have a public endpoint to update an existing action item's status (as far as I can tell). * Manual process: Having a team rule to update both places. Spoiler: it's not followed consistently. * Using only Jira for tracking: Loses all the meeting context and notes from Fellow. My big question for the community: **Has anyone successfully hacked together a bi-directional sync?** I’m wondering if: 1. You’ve found a middleware (like an automation tool) that can bridge this gap, perhaps by using webhooks from Jira and somehow updating Fellow through a creative use of their API? 2. You’ve convinced your team to adopt a different workflow that makes the one-way sync work seamlessly? 3. You’re using a different app entirely that handles this meeting-to-project-tracking loop better? I’m particularly interested from a martech/ops perspective, where we often sit between sales (who live in Fellow/meetings) and product/engineering (who live in Jira). Any insights, shared experiences, or even commiseration would be super helpful!

Page 3 / 3 Prev

Fellow Reviews

Last Post by Anna B 58 minutes ago

31 Posts

30 Users

0 Reactions

6 Views

RSS

Anna B

(@annab8)

Active Member

Joined: 1 day ago

Posts: 8

30/07/2026 7:30 pm

Oh yeah, the missing update endpoint is the killer. I feel you on wanting that loop closed.

We tried to force a bi-directional sync early on and it was a mess of Zapier filters and false states. The manual check-off felt like a step backward, but honestly, it became our forcing function to actually review the *outcome* in the weekly sync, not just the status change. It stopped us from blindly trusting a Jira "Done" when the action item was actually only half-baked.

Maybe reframe it? The one-way sync ensures the action item is created accurately from the meeting. The manual closure is the quality gate.

ReplyQuote

Page 3 / 3 Prev