Hire Make.com Developer

[Carl_Smith]

I’m looking for a Make.com expert to help me build a simple but precise API integration across my current stack.

Current Workflow:

• Data is prepared and loaded into Google BigQuery (via Alteryx).

• Softr is used as the front-end to read from BigQuery tables.

Goal:
When a user clicks a button in Softr, it should:

1. Trigger a Make.com webhook (or custom endpoint).

2. Use the row_id (or primary key) passed from Softr to query BigQuery for that single record.

3. Send that record to SmartSuite by creating a new record through the SmartSuite API.

   • Must include required authentication headers:

     • Authorization: Token <API_KEY>

     • Account-Id: <WORKSPACE_ID>

   • Must correctly map fields from BigQuery to SmartSuite’s field API keys.

Key Requirements:

• Build the Make.com scenario:

  • Webhook trigger from Softr.

  • BigQuery “Execute Query” (parameterized by ID).

  • HTTP POST to SmartSuite /records endpoint.

• Handle errors and duplicates (e.g., prevent duplicate SmartSuite records if a button is clicked twice).

• Return a Webhook Response so Softr can display success/failure feedback to the user.

• Document the final setup (steps, mapping, and where to insert API keys).

Deliverables:

• Working Make.com scenario that does the above end-to-end.

• Short documentation or walkthrough (how to maintain/update).

Nice to Have:

• Logging results (status + recordId) back into BigQuery.

• Error handling/retry logic in Make.com.

[andres]

Carl, we can help.
Let’s meet on Zoom to go over the details. Book a time of us here https://connex.digital/book/make

Talk soon!

[Pathfinder_Automate]

Hello @Carl_Smith , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications

[mital_patel]

Hi Carl,

I’d be happy to help you build and document this Make.com workflow. I’ve developed multiple Make.com scenarios integrating APIs, BigQuery, and no-code tools like Softr, Airtable, and SmartSuite, so I’m confident I can deliver a clean, reliable solution for your stack.

Here’s how I’d approach it:

• Webhook Trigger: Configure a Make.com webhook (or custom endpoint) to accept Softr’s button click and pass the row_id.

• BigQuery Query: Set up a parameterized query to fetch the exact record from BigQuery.

• SmartSuite Integration: Map fields precisely and send the record via HTTP POST to /records, including required Authorization and Account-Id headers.

• Duplicate Handling: Add logic to prevent duplicate entries if the button is clicked multiple times.

• Webhook Response: Return success/failure feedback back to Softr for a better user experience.

• Documentation: Provide a clear walkthrough with mapping, authentication notes, and update instructions.

Optional Enhancements:

• Log results (status + recordId) back into BigQuery for auditing.

• Implement retry/error handling within Make.com to ensure robustness.

I can deliver a working end-to-end scenario with short documentation, ensuring it’s easy for your team to maintain.

Do you already have API keys and access tokens set up for SmartSuite, or would you like me to assist with that as well?

[Greatness_me]

Hey @Carl_Smith , I see exactly what you need. A Softr button → Make.com webhook → BigQuery lookup → SmartSuite record creation with error handling, dedupe protection, and clean success/failure feedback back to the user. That’s the kind of end-to-end automation I specialize in.

I’ve built similar Make.com workflows connecting CRMs, APIs, and databases where the key was precise field mapping, safe retries, and clean webhook responses so the front-end experience feels seamless. I’d set this up with structured error handling, deduplication checks, and clear documentation so your team can easily update API keys or mappings in the future.

I can also add the “nice to have” logging results/status back into BigQuery so you have a full audit trail of every run.I’m looking for a Make.com expert to help me build a simple but precise API integration across my current stack.

Let’s have a chat about this. You can schedule a call with me here.

@Carl_Smith

Current Workflow:

• Data is prepared and loaded into Google BigQuery (via Alteryx).
• Softr is used as the front-end to read from BigQuery tables.

Goal:
When a user clicks a button in Softr, it should:

1. Trigger a Make.com webhook (or custom endpoint).
2. Use the row_id (or primary key) passed from Softr to query BigQuery for that single record.
3. Send that record to SmartSuite by creating a new record through the SmartSuite API.

• Must include required authentication headers:
  • Authorization: Token <API_KEY>
  • Account-Id: <WORKSPACE_ID>
• Must correctly map fields from BigQuery to SmartSuite’s field API keys.

Key Requirements:

• Build the Make.com scenario:
  • Webhook trigger from Softr.
  • BigQuery “Execute Query” (parameterized by ID).
  • HTTP POST to SmartSuite /records endpoint.
• Handle errors and duplicates (e.g., prevent duplicate SmartSuite records if a button is clicked twice).
• Return a Webhook Response so Softr can display success/failure feedback to the user.
• Document the final setup (steps, mapping, and where to insert API keys).

Deliverables:

• Working Make.com scenario that does the above end-to-end.
• Short documentation or walkthrough (how to maintain/update).

Nice to Have:

• Logging results (status + recordId) back into BigQuery.
• Error handling/retry logic in Make.com

I see exactly what you need — Softr button → Make.com webhook → BigQuery lookup → SmartSuite record creation — with error handling, dedupe protection, and clean success/failure feedback back to the user. That’s the kind of end-to-end automation I specialize in.

I’ve built similar Make.com workflows connecting CRMs, APIs, and databases where the key was precise field mapping, safe retries, and clean webhook responses so the front-end experience feels seamless. I’d set this up with structured error handling, deduplication checks, and clear documentation so your team can easily update API keys or mappings in the future.

I can also add the “nice to have” logging results/status back into BigQuery so you have a full audit trail of every run.

[Farhan_Ahmed]

Hi, I’m a Make.com expert with experience building precise API integrations and automations. I can help you connect Softr → BigQuery → SmartSuite so that when a user clicks a button in Softr, the correct record is fetched from BigQuery and sent to SmartSuite automatically. I also handle error prevention, duplicate checks, and can provide clear documentation for maintenance.

You can check out my profile here: https://www.upwork.com/freelancers/farhana401

Or directly book a call here:https://calendly.com/automaxion-meet

[deepvyas]

@Carl_Smith

looking for a Make.com expert to help

Hi @Carl_Smith
I am available for your assistance further.
Please let me know suitable time to discuss here

Regards
Deep

[Hashlogics]

Hi @Carl_Smith
I can deliver an end-to-end Make.com scenario connecting Softr → BigQuery → SmartSuite with idempotency, error handling, and a webhook response back to Softr.

Implementation plan (precise + minimal)

1. Trigger

   • Make Webhooks > Custom Webhook receives row_id (primary key) from Softr button.

   • Validate payload; reject if missing/invalid.

2. Fetch from BigQuery

   • Google BigQuery > Execute a SQL query with a parameterized query:

     SELECT * FROM <dataset>.<table> WHERE row_id = @row_id LIMIT 1
     
     

   • Fail fast if zero or >1 records.

3. Duplicate prevention

   • Compute an idempotency key (e.g., hash(row_id)) and check a Make Data Store (or a SmartSuite unique field) before POSTing.

   • If already processed, short-circuit to “Already synced” response.

4. Create SmartSuite record

   • HTTP > Make a request

     • Method: POST to https://api.smartsuite.com/v1/records (or your base URL).

     • Headers:

       • Authorization: Token <API_KEY>

       • Account-Id: <WORKSPACE_ID>

       • Content-Type: application/json

     • Body: map BigQuery fields → SmartSuite field API keys (I’ll document each mapping).

5. Webhook Response to Softr

   • Webhooks > Response returns JSON: status, recordId (from SmartSuite), message.

6. Observability & hardening (nice-to-have)

   • Logging: write status + recordId + timestamp back to BigQuery (Insert row).

   • Retries: Make error handler route with limited backoff for transient 429/5xx.

   • Security: keys stored in Make connections/variables; no secrets in plain text.

   • Docs: brief runbook (steps, env vars, mapping, where to put keys).

Deliverables

• A working Make scenario (Softr → BigQuery → SmartSuite) with duplicate protection and webhook response.

• Short documentation (setup, field mapping, API key placement, maintenance).

• Optional: BigQuery logging + retry strategy.

Effort & rate

• Core flow (Steps 1–5): 4–6 hours

• Logging + retries + polish: +2–3 hours

• Rate: $30/hr. If you prefer, I can quote a fixed fee after a 10-min scope check.

Quick confirmations to start

1. Softr passes which parameter name? row_id, id, or something else?

2. BigQuery dataset/table names and the exact primary key field.

3. SmartSuite solution & table (and any required field API keys).

4. Should we enforce uniqueness in SmartSuite (unique field) or via Make Data Store (or both)?

5. Expected volume / button click frequency (to size retries/rate limits).

If you share the BigQuery schema (1 sample row) and the SmartSuite field keys, I can begin immediately and ship the first run within the same day.

—
Abdul Basit
CEO, Hashlogics
Portfolio: https://hashlogics.com/portfolio
Case Studies: https://drive.google.com/file/d/1MZLCwijnWGXXjwLx3uXBcwz7D81pl6d2/view
Reviews: https://clutch.co/profile/hashlogics
Call: https://calendly.com/_hashlogics/abdul-basit