peterpiper•3mo ago

REST API connection between BuildShip and SmartSuite

I don't suppose anyone has managed to create a connection between BuildShip and SmartSuite? It needs both an authorisation token and and Account ID so it doesn't perfectly match the videos I have found. I tried the AI assistant which made some changes (along the lines of Bearer ${ctx.root.auth_token}, Account-ID: ${ctx.root.account_id} but still no joy.

4 Replies

peterpiper•3mo ago

The most common error I am getting (there have been a few as I bash away at a fix) is Unexpected token 'A', "Account ID"... is not valid JSON This is the info I could find in the SmartSuite guide...... Authentication SmartSuite uses simple token-based authentication. You can generate or manage your API key in your User Profile. All API requests must be authenticated and made over HTTPS. IMPORTANT! Your API key conveys the same privileges as the Member account it is generated in, so it should be treated as securely as a password. You authenticate to the API by providing your API key in the Authorization header, as well as your Workspace Id in an Account-Id header, as shown below. KEY:VALUE Authorization: Token API_KEY_HERE Account-Id: WORKSPACE_ID_HERE NOTE: Your Workspace Id is the 8 characters that follow https://app.smartsuite.com/ in the SmartSuite URL when you’re logged in. Example: https://app.smartsuite.com/sv25cxf2/solution/62c4b…

AI Support•3mo ago

To create a connection between BuildShip and SmartSuite, you need to ensure that the headers and the body of your request are correctly formatted. The error you're seeing, "Unexpected token 'A', 'Account ID'... is not valid JSON," indicates that there might be an issue with how the headers are being included in your request. Here's a step-by-step guide on how to set up your connection properly: 1. Set Up Your Headers: Ensure that your headers include both the authorization token and the account ID in the correct format. For example:

   {
     "Authorization": "Bearer YOUR_AUTH_TOKEN",
     "Account-ID": "YOUR_ACCOUNT_ID",
     "Content-Type": "application/json"
   }

   {
     "Authorization": "Bearer YOUR_AUTH_TOKEN",
     "Account-ID": "YOUR_ACCOUNT_ID",
     "Content-Type": "application/json"
   }

2. Create a Workflow with HTTP Request Node: Use the HTTP Request node in BuildShip to make the API call to SmartSuite. Configure the node to include the headers you set up in the previous step. 3. Check the Request Body: Ensure that the body of your request, if required, is also correctly formatted as JSON. For example:

   {
     "key1": "value1",
     "key2": "value2"
   }

   {
     "key1": "value1",
     "key2": "value2"
   }

4. Test the Workflow: Test the workflow to ensure that the request is being sent correctly and that the response from SmartSuite is as expected. For more detailed information on how to configure HTTP requests and handle authentication in BuildShip, you can refer to the official documentation: BuildShip API Documentation. If you continue to experience issues, you might want to double-check the SmartSuite API documentation to ensure that you are using the correct endpoints and request formats. Source: BuildShip API Documentation

Welcome to BuildShip – BuildShip

A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.

AI Support•3mo ago

Certainly! You can watch the BuildShip "Generate with AI" YouTube video using the following link: !BuildShip Generate with AI Video For more detailed information, you can refer to the documentation on building custom nodes via AI in BuildShip: BuildShip AI Generated Nodes Documentation Source: https://docs.buildship.com/ai-nodes

BuildShip

YouTube

Generating Custom Nodes with AI - BuildShip AI Workflow Builder

Get started with BuildShip for FREE 👉 https://buildship.com A Low-code Visual Backend Builder with AI 💬 Chat and build together with a community of no-code/low-code developers: https://buildship.com/discord 🐦 Tweets: https://twitter.com/buildshipapp #nocode #backend #apibuilder #lowcode #cronjob #scheduledtask #backgroundjob #googlecloud #ope...

AI Generated Nodes – BuildShip

A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.

peterpiper•3mo ago

Hi - thanks for that - I am guessing the syntax changes a little bit if I am using the "Secrets" functionality.... the attempt below still generates that same error so I must have formed it incorrectly { "Authorization": (await getSecret("SmartSuiteKey")), "Account-ID": (await getSecret("SmartSuiteAccount")), "Content-Type": "application/json" } Weirdly, I just tried setting up the API Call in Flutterflow direct and it worked first time!