Integrating with jotform.com or pipedream.com [Apr 01]

NocoDB · November 3, 2022, 8:51am

Hello, my name is Daniel

Please let me know if this the the wrong channel for the following question.

I’m currently doing user research and prototyping in the context of refugee support (e.g. doing mobile distributions of aid items in the Balkan route in Europe and in the Ukraine context).

For a current use case, I was wondering: are there any experiences, examples, best practices etc for connecting a NocoDB instance with jotform.com and/or pipedream.com?

NocoDB · November 3, 2022, 8:51am

hey Daniel, welcome

you can have a look at our API documentation

NocoDB · November 3, 2022, 8:51am

Thanks!

I did, I know about Web Hooks (they seem to be atm more outgoing so - so informing external APIs about data changes within NocoDB, but not the other way around).

And I know about GraphQL (e.g. mutations) and REST-API capabilities.

NocoDB · November 3, 2022, 8:51am

(side question: is it possible to have both GraphQL AND REST for the same project?)

NocoDB · November 3, 2022, 8:51am

if you are looking at meta APIs (like API to get tableColumns), these are undergoing changes as we speak. And new APIs will be available early next week.

Ah - so for the incoming webhooks. You can use our APIs with API Token

NocoDB · November 3, 2022, 8:51am

https://docs.nocodb.com/developer-resources/api-tokens

NocoDB · November 3, 2022, 8:51am

great - thanks! That’s the confirmation I needed regarding the right direction.

NocoDB · November 3, 2022, 8:51am

(last thing - short answer to “Is it possible to have both GraphQL AND REST for the same project?” would also be super helpful :))

NocoDB · November 3, 2022, 8:51am

nope

NocoDB · November 3, 2022, 8:52am

thanks!

NocoDB · November 3, 2022, 8:52am

we 're planning to stop gql as its a very small use case for our users and not the best fit for building smartspreadsheets

NocoDB · November 3, 2022, 8:52am

would love to know the requirement of gql

NocoDB · November 3, 2022, 8:52am

oh that’s sad! the gql support sounds (without having using NocoDB yet, so based on new-user perspective) like an extremely nice feature, even important.

Simply for having the ability of using NocoDB as a BE with Apps and web apps, also with GraphQL and it’s advantages and ecoystem on the client world

NocoDB · November 3, 2022, 8:52am

(but I understand that there are a lot of priorities to juggle I guess )

NocoDB · November 3, 2022, 8:52am

I guess REST would work for almost al use cases as well

NocoDB · November 3, 2022, 8:52am

we may think about it in future it. The reason being : spreadsheet are flat pieces of information in a way even when we create lookups and rollups. And gql has deeply nested jsons. So its additional work to render the GUI and maintain the schema as users change the structure dynamically

NocoDB · November 3, 2022, 8:52am

got it

NocoDB · November 3, 2022, 8:52am

might also be biased a bit about GraphQL because of it’s hype - easy to forget that REST still works well in a lot cases as well

NocoDB · November 3, 2022, 8:52am

thank you

NocoDB · November 3, 2022, 8:52am

Topic		Replies	Views
GraphQL Support [Jul 25] Discord-Discussions	8	191	November 3, 2022
API docs [Feb 05] Discord-Discussions	20	226	November 3, 2022
Rest API [Aug 05] Discord-Discussions	4	182	November 3, 2022
V0.90 Important Announcement Announcements	0	578	March 31, 2022
Important announcement to changes our API [Apr 01] Discord-Discussions	2	156	November 3, 2022

Integrating with jotform.com or pipedream.com [Apr 01]

Hello, my name is Daniel

Please let me know if this the the wrong channel for the following question.

I’m currently doing user research and prototyping in the context of refugee support (e.g. doing mobile distributions of aid items in the Balkan route in Europe and in the Ukraine context).

For a current use case, I was wondering: are there any experiences, examples, best practices etc for connecting a NocoDB instance with jotform.com and/or pipedream.com?

hey Daniel, welcome

you can have a look at our API documentation

Thanks!

I did, I know about Web Hooks (they seem to be atm more outgoing so - so informing external APIs about data changes within NocoDB, but not the other way around).

And I know about GraphQL (e.g. mutations) and REST-API capabilities.

(side question: is it possible to have both GraphQL AND REST for the same project?)

if you are looking at meta APIs (like API to get tableColumns), these are undergoing changes as we speak. And new APIs will be available early next week.

Ah - so for the incoming webhooks. You can use our APIs with API Token

https://docs.nocodb.com/developer-resources/api-tokens

great - thanks! That’s the confirmation I needed regarding the right direction.

(last thing - short answer to “Is it possible to have both GraphQL AND REST for the same project?” would also be super helpful :))

nope

thanks!

we 're planning to stop gql as its a very small use case for our users and not the best fit for building smartspreadsheets

would love to know the requirement of gql

oh that’s sad! the gql support sounds (without having using NocoDB yet, so based on new-user perspective) like an extremely nice feature, even important.

Simply for having the ability of using NocoDB as a BE with Apps and web apps, also with GraphQL and it’s advantages and ecoystem on the client world

(but I understand that there are a lot of priorities to juggle I guess )

I guess REST would work for almost al use cases as well

we may think about it in future it. The reason being : spreadsheet are flat pieces of information in a way even when we create lookups and rollups. And gql has deeply nested jsons. So its additional work to render the GUI and maintain the schema as users change the structure dynamically

got it

might also be biased a bit about GraphQL because of it’s hype - easy to forget that REST still works well in a lot cases as well

thank you

Related Topics