search

hasura / data-hub

Explore data sources from a native GraphQL API, database schemas to custom code contributed by the community.
https://hasura.io/data-hub/
MIT License
26 stars 16 forks source link

DailyKIT Offered Remote Schemas #6

Open futuregridtechnologies opened 3 years ago

futuregridtechnologies commented 3 years ago

Hey,

At Dailykit, we're using Hasura to power our backend requirements completely and have done some remote schemas to be used with Hasura.

We have following remote schemas available which are open source.

  1. dailyGIT (it's a git integrated filesystem that allows you to create read, update, delete files and folders and can commit based on request)
  2. Ohyay (Its a zoom equivalent streaming service that allows creation of workspaces and invite links)
  3. Ayrshare (It's a company that allows a dedicated integration with all social media to manage posts and comments)
  4. Twilio SMS (sendSMS action)
  5. nodemailer (sendEmail Action) includes ability to send attachments and invites and part of global header and footer templates.
  6. Stripe (setup intent, payment method, payment intent, invoices)
  7. Rule Engine (A postgres based rule engine that allows recursive and or condition functions which can be used as a computed field to put a conditional logic). At Dailykit, we use it for coupons.
  8. SQL functions to create hasura scheduled events internally.
  9. Tracked views that show all the pg_catalog and hdb_catalog data and is linked through relations so can be used to read hierarchial data.

We'd love to contribute them and showcase them through hasura with a chance to return something back to community.

Check us out at github.com/dailykit

praveenweb commented 2 years ago

Hey @futuregridtechnologies!

This is great! We have started adding more integrations to our Data Hub. It is interesting to see your usage of various Actions and Events and would love to feature them on our Data Hub.

How do you think we should take this forward? If possible, you can create a PR to this repo to the respective action/event transform directories. Else, you could also update the config.json to point to an OSS repo that you have the above integrations working.