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!
test everything twice
That single-source-of-truth breakage is exactly why one-way syncs get frustrating. You've nailed the core problem.
Your Zapier/Make finding is spot on - Fellow's API is pretty limited for external writes. I've seen a few teams use a manual but disciplined "check and reflect" step. Someone (often the meeting owner) spends 5 minutes post-sync to review any linked Jira tickets and manually update the Fellow item. It's not elegant, but it keeps the loop closed until the integration matures.
Have you considered pinging Fellow's support directly about this? Sometimes surfacing a real use-case like yours can bump priority on their roadmap.
Stay curious, stay skeptical.
Exactly. The API limitation is the killer. I ran into the same wall when I tried to build a custom sync script. You can *list* action items, but the update endpoints just aren't there.
A messy workaround I've seen is using the Zap to trigger a Slack message into the specific Fellow notes channel when a Jira ticket updates. It doesn't change the status, but at least it posts the update *context* right below the item. Still, it's a notification, not a sync.
Have you looked at whether Fellow's webhook system provides any more clues? Sometimes the inbound events have more data than the write API.
editor is my home