Is it possible to export data from Quickbase via alteryx?
we have our own quickbase site...
www.companyname.quickbase.com
@jbravman_,
A quick google of "Quickbase API" returns this hit: https://help.quickbase.com/api-guide/index.html
You might be the first to build a connector macro to it.
Cheers,
Mark
https://companyname.quickbase.com/db/[TableId]
2. Add a Download tool to the Text Input tool.
Name Value
a API_DoQuery
usertoken [usertoken] /*can be created in quickbase - see quickbase documentation*/
apptoken [Your App Token] /*ask your admin to create one for you*/
3. Then connect this download tool to a XML Parse tool.
You can try to put the following URL in any browser to see xml data
https://companyname.quickbase.com/db/[TableId]?a=API_DoQuery&fmt=structured&usertoken=[Your User Token]&apptoken=[Your App Token]
Reddy, I just ran across this post because I'm also trying to connect to QuickBase using API.
When I try what you have posted below, I receive the error
Error transferring data: Failure when receiving dat from peer.
Do you have any ideas what the issue could be?
Hello, wondering if we can extract the data via JSON query?
I also would like to know how to work with the Quickbase JSON RESTful API in Alteryx. REF: Quickbase API Portal
Have you figured this out?
I figured out how to use the Quickbase RESTful JSON API. Documentation: Quickbase API PortalText Input shape1 Row, 2 Columns: EndpointURL; JSONbody
EndpointURL like https://api.quickbase.com/v1/records/query
JSONbody like Sample Request example (see documentation)Download shape
Basic TabField set to EndpointURLOutput To a Field, String, Data Encoded As Unicode UTF-8Headers TabQB-Realm Host Name, User-Agent, Authorization, and Content-Type (see documentation)Payload TabTake Query String/Body from Field: JSONbodyJSON Parse shapeJSON Field, DownloadData, Output values into single string fieldNote that each attribute of each object returned in the response (JSON array) is listed as a "record" coming out of the JSON Parse step. For example, if six text fields are selected from each record, you get six rows (records).
Similarly, the Record Owner field when returned results in rows for each attribute contained therein (email, id, and name). I included six field IDs in my select statement including Record Owner and Last Modified By (both users with three attributes each), so I got four + three + three (10) rows for each QB record.
