I have managed to build a few custom pipes (One for [Texting/SMS)(http://www.cadoo.com) and another for eSig using docuseal.co.
These were relatively straightforward.
I now need to integrate to NestForms API but this uses OATH2.0 for authentication
It looks like tadabase custom pipes don’t support OATH2.0
Please note: OAuth 2.0 is not supported when Adding Custom Pipes.
I was wondering if anybody had managed a work around or could provided some advise
Hi Moe … I will talk to the NestForms Developer also and see if there are other options.
Its a pretty unique forms software and I looked at loads ( mobile app, custom database, API, Web hooks, custom pdf ) and they are even planning on adding a “Canvas” component that will allow my client create a simple drawing of the planned openings for new windows and doors for surveys.
Anyway big ask for you to look at integration , thanks for thinking about it … I will see what I can with the developer also
(Not sure why they used OATH2 its very complex compared to the other Saas I have managed to integrate via Pipes)
Hi All,
As pre previous post a while back I am integrating a really flexible piece of survey software called NestForms https://www.nestforms.com into my tadabase APP.
Essentially, I am sending some quotation data from by TB app to NestForms backend database so that the assigned sales rep can conduct the related survey in the app.
(The sales rep will select a quote from the quotes table that they want to do a survey for, press the button (trigger pipe) that sends data to NestForms.
They need to do this as not all jobs are surveyed, and it also “tags” the entry in the Nest Forms database for them.
Unfortunately, Nest API uses OAUTH2 for authentication (with expiring tokens), so I have had to attempt to build this using Pipes etc.
I have actually made some good progress on this.
Using private credentials in a custom component, I request an Authorization Code which I get back via a custom component. This is a one-off activity really so no worries there.
I have a (for now a manually triggered) pipe that uses this Auth Code to request an Access Token and Refresh Token and insert into a one row “Auth” table.
I manually use the access token to request/Update the data in Nest via pipe.
However, the Access token dies after 60 min. The Refresh token dies after 1 month.
Therefore, I have to request a new Access token using the Refresh token via a Pipe.
This then provides a new Access Token and a new Refresh token which I store in my one row “Auth” table (over writing old codes).
This starts the clock on both Access token (60 min) and Refresh token (1 Month) again.
I have multiple users on the system. Only one Access token works at a time so must be shared between all users.
I need
a way to keep the Access Token refreshed (or refresh it, if it is expired)
a way to pass this token into my manually triggered pipe
I thought I might be able to trigger a pipe every 50 mins from the scheduler, but that frequency is not possible in Tadabase. No clue yet how I might pass the Access Token to the pipe
Well the tough ones are probably the most rewarding !!!
Objective:
Send Contact details from my Quotes table to NestForms Survey Software Custom database. This allows surveyor to select job from drop down and populate all job info (rather than having to re type)
Problem
NestForms using Auth2 to authenticate read/writes via API
Solution
Once I had the initial Refresh Token I stored this in a one row AUTH Table.
(This is essentially a “global variable” that I can read and write to)
I then set up series of chained triggers (on Quotes) using an Action Rule:
Reads the latest refresh code from Auth (Tadabase REST API Get a Single record) and write this to a field in the Quotes row (this is just for temp use).
I then run API call to get a new Access code from Nest which also gives you a new Refresh Code. I store both of these in Quotes Table.
I then send the quote details to Nest via API using current Access Code.
I then update the central Auth2 record (Tadabase API Update Existing Record) with the latest Refresh code so that this can be used for next update
Hopefully this is of some use to somebody looking to “hack” together a home grown AUTH2 authentication. Probably should work for low/mid volume. Will see how it goes