# Github Issues \<--\> Baserow Synchronization

**URL:** <https://community.baserow.io/t/github-issues-baserow-synchronization/1527>\
**Category:** Feature Ideas\
**Tags:** brainstorm, use-case\
**Created:** [October 5, 2022, 2:31pm UTC](https://community.baserow.io/t/github-issues-baserow-synchronization/1527 "2022-10-05T14:31:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bfranklin](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/59ef9b/32.png) [@bfranklin](https://community.baserow.io/u/bfranklin)\
**Post date:** [October 5, 2022, 2:31pm UTC](https://community.baserow.io/t/github-issues-baserow-synchronization/1527/1 "2022-10-05T14:31:39Z")

</div>

I am really loving Baserow. It’s increasingly shaping up to be a central hub for me. That said, given that the project is still young it seems it’s also young on synchronization integrations. Specifically, I would love to be able to have a two-way synch between github issues for repositories and Baserow.

There are companies like Unito that do this but they focus on the big task managers like Clickup and Asana and Basecamp and Jira.

Just putting this out there in case anyone has any early success on creating two-way synchronizations for Baserow.

---

<div class="post-metadata">

**Author:** ![olgatrykush](https://community.baserow.io/user_avatar/community.baserow.io/olgatrykush/32/219_2.png) [@olgatrykush](https://community.baserow.io/u/olgatrykush)\
**Post date:** [October 11, 2022, 3:05pm UTC](https://community.baserow.io/t/github-issues-baserow-synchronization/1527/2 "2022-10-11T15:05:18Z")

</div>

Hello again @bfranklin!

As explained here: [Table synchronization between different bases (Use case explained) - #6 by olgatrykush](https://community.baserow.io/t/table-synchronization-between-different-bases-use-case-explained/1419/6), the first step for us would be to brainstorm session on the syncing mechanisms we will use. If I have any updates on this topic, I’ll post them in the community 👌

---

<div class="post-metadata">

**Author:** ![joffcom](https://community.baserow.io/user_avatar/community.baserow.io/joffcom/32/610_2.png) [@joffcom](https://community.baserow.io/u/joffcom)\
**Post date:** [November 11, 2022, 7:14am UTC](https://community.baserow.io/t/github-issues-baserow-synchronization/1527/3 "2022-11-11T07:14:19Z")

</div>

Hey @bfranklin,

What sort of thing are you thinking of? Going from GitHub to Baserow sounds easy enough but what would you want to sync back to GitHub?

---

<div class="post-metadata">

**Author:** ![bfranklin](https://community.baserow.io/letter_avatar_proxy/v4/letter/b/59ef9b/32.png) [@bfranklin](https://community.baserow.io/u/bfranklin)\
**Post date:** [November 16, 2022, 7:56pm UTC](https://community.baserow.io/t/github-issues-baserow-synchronization/1527/4 "2022-11-16T19:56:09Z")

</div>

I just want to be able to spend all my time in Baserow and not have to switch to Github to look at the latest issues or change their status or comment on them. Products like Unito ([https://unito.io/https://unito.io/](https://unito.io/https://unito.io/)) do this sync for the big apps like Airtable and Clickup and Asana but haven’t written a two-way sync for Baserow … I have thought about trying it myself using Pipedream but haven’t take the time to learn Pipedream yet. Looks cool though.

---

<div class="post-metadata">

**Author:** ![joffcom](https://community.baserow.io/user_avatar/community.baserow.io/joffcom/32/610_2.png) [@joffcom](https://community.baserow.io/u/joffcom)\
**Post date:** [November 19, 2022, 12:10pm UTC](https://community.baserow.io/t/github-issues-baserow-synchronization/1527/5 "2022-11-19T12:10:13Z")

</div>

@bfranklin I was thinking it could probably be done with n8n as well and I could get an example together if you had a specific set of requirements to start with.