Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow group/assurances to be updated in Airtable when OFN listing is updated. #83

Open
karlafalk opened this issue Sep 17, 2024 · 3 comments

Comments

@karlafalk
Copy link

Thanks @mkllnk for this last n8n workflow that allows updates to flow from OFN to the Airtable/directory.

I have now been able to get it working for the Waterloo project. However, it looks like the ability to 'update' group membership/assurance has not been connected in the workflow, and was only added in concept. So if an user removes themselves from a group on OFN, then after triggering the 'update listing' workflow, this change wouldn't correspondingly be reflected in Airtable.
Image

Just wondering there are any updates on the completion of this step? Are there plans to connect this part of the workflow for the AUS project? It is not critical for the Waterloo Project, but we wanted to check the status of this element that would allow the listing to be fully updated in Airtable. Thanks!

@karlafalk karlafalk converted this from a draft issue Sep 17, 2024
@mkllnk
Copy link
Member

mkllnk commented Sep 24, 2024

Good question! We never completed that. I guess that those assurances are handled manually in Airtable. I'll ask the team.

@David-OFN-CA
Copy link
Collaborator

Cheers @mkllnk - just trying to close the loop on this so, did the Aus team have any feedback to offer on this point?

@mkllnk
Copy link
Member

mkllnk commented Oct 1, 2024

Yes, all handled manually for now. We need more experience with the partners to find a better process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

3 participants