Operations & Internal Tools
Connect SmartSuite and Make
SmartSuite holds the record. Make carries it everywhere else, inside the API quota.
- Connects
- SmartSuite and Make
- Data flows
- 4 automated, two-way where safe
- Built with
- SmartSuite API, Make, Shopify
- Timeline
- Live in 3 to 5 business days from scope
- Owned by
- You. Accounts, credentials and code in your name.
In short
Connecting SmartSuite and Make keeps one record in SmartSuite and lets Make scenarios push it to sales channels, file quote revisions and send reminders. SBD has built both patterns: a product sync to Shopify and eBay, and quotation management with reminders. Make calls count against your SmartSuite API quota, so design matters.
The workflows
What runs between SmartSuite and Make.
Each line is one automated workflow. An event in one tool, the checks and mapping in between, the action in the other, and the person who hears about it.
-
One product record, every channel
WhenA product record changes in SmartSuite
Automation- Verify and validate
- Map and normalise
- Upsert by key
ThenMake maps it to each channel format and pushes it to Shopify and eBay, resizing images per platform
And- Audit log entry
- Alert if it fails or goes quiet
- Review queue if unsure
-
Sales on Shopify reflected everywhere
WhenAn order is placed on Shopify
Automation- Verify and validate
- Map and normalise
- Upsert by key
ThenMake updates stock on the SmartSuite record and on every other channel
And- Audit log entry
- Alert if it fails or goes quiet
- Review queue if unsure
-
Quote revisions filed under the project
WhenA new or revised quote is logged from a mobile form
Automation- Verify and validate
- Map and normalise
- Upsert by key
ThenFile it under its project with a timestamped revision, keeping every earlier version
And- Audit log entry
- Alert if it fails or goes quiet
- Review queue if unsure
-
Next actions that remind their owner
WhenA next action or meeting falls due
Automation- Verify and validate
- Map and normalise
- Upsert by key
ThenMake sends the owner a reminder by email, WhatsApp or Slack
And- Audit log entry
- Alert if it fails or goes quiet
- Review queue if unsure
Every record passes through the same stages
- 1Receive
Webhook or polling from the source tool, with a signed payload and a replay log.
- 2Validate
Required fields present, types right, record key found. Anything else goes to the review queue.
- 3Map
Fields translated to the destination schema. Enumerations, currencies and dates normalised.
- 4Upsert
Written against the record key, so a retry updates rather than duplicates.
- 5Confirm
Outcome logged. Alert if the count goes quiet. Reconciliation run nightly.
Read this first
Why the obvious route breaks.
A one-step Zap connects SmartSuite and Make in an afternoon. This is what goes wrong once real volume and real edge cases arrive.
Make calls count against the SmartSuite quota
SmartSuite says calls made by Make and similar tools count against the workspace quota: 25,000 requests a month on Team, 100,000 on Professional and 500,000 on Enterprise. At 100% calls slow to 2 a second per user, and at 125% API access stops until the next billing cycle. A scenario that re-reads the whole table each run finds that limit fast.
Five requests a second, then a 30-second wait
The SmartSuite API allows 5 requests a second per API key. Exceed it and you get a 429 and must wait 30 seconds. A bulk price change that fires one Make run per record hits this at once, so bulk modules and a deliberate pace are part of the build.
Every channel wants a different shape
In the watch reseller build, eBay, Shopify and Chrono24 each had their own rules for titles, categories and images. A scenario that copies fields straight across creates listings that fail or read badly. The per-channel translation is the real work, not the trigger.
Failed runs vanish unless you keep them
Make can store a failed run as an incomplete execution so it can be fixed and resumed, and can process runs in order. Both are settings, not defaults you can assume. Without them a failed stock update is lost, and a later run can overwrite a newer one.
What it costs today
The gap, as the team feels it and as the engineer sees it.
In the team
- The same product is edited on three storefronts
- A watch sells on one channel and stays live on another
- Quote files live in folders nobody can find
- Follow-ups happen when someone remembers
- Launching a product takes hours
Under the hood
- Make calls count against the SmartSuite monthly quota
- 5 requests a second per key, then a 30-second wait
- Per-channel title, category and image rules
- Failed runs lost unless incomplete executions are stored
- Order of updates matters for stock
What we wire up
The data flows.
- 01 When
A product record changes in SmartSuite
ThenMake maps it to each channel format and pushes it to Shopify and eBay, resizing images per platform
- 02 When
An order is placed on Shopify
ThenMake updates stock on the SmartSuite record and on every other channel
- 03 When
A new or revised quote is logged from a mobile form
ThenFile it under its project with a timestamped revision, keeping every earlier version
- 04 When
A next action or meeting falls due
ThenMake sends the owner a reminder by email, WhatsApp or Slack
Used for
- One product record, every channel
- Sales on Shopify reflected everywhere
- Quote revisions filed under the project
- Next actions that remind their owner
- SmartSuite to Shopify product sync
- SmartSuite to eBay listings
- Quotation management on SmartSuite
- Make reminders by email, WhatsApp and Slack
- Brands and architects in one workspace
- Inventory kept in step across channels
Built with
Data map
What becomes what, and what it is keyed on.
| In SmartSuite | In Make | Matched on | Direction |
|---|---|---|---|
| Product records | Shopify and eBay listings via Make | SKU | one-way |
| Stock level | Channel inventory, updated from orders | SKU | two-way |
| Quotation records and file revisions | Project record with revision history | SmartSuite record ID | one-way |
| Next action and meeting dates | Reminder by email, WhatsApp or Slack | Owner and record ID | one-way |
Field-level mapping is agreed in the blueprint and written into the runbook. Two-way rows carry loop protection so a write from the sync never re-triggers the sync.
In every build
What you get with the sync, whichever pair.
Under the hood
- Upserts keyed on the record
Every write is matched on the source ID. A retry or a re-fire updates the existing record instead of creating a second one.
- Retries with backoff
Rate limits and timeouts are retried with increasing delays, then parked for review, never dropped.
- Idempotent, loop-safe writes
Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.
- Reconciliation
A nightly job compares counts and totals on both sides and lists any record that differs.
- Audit log
Every run records input, mapping result, action taken and who or what triggered it. Searchable by record.
- Error monitoring
Loud failures alert within minutes. Quiet ones are caught by an outcome count that alerts when it stops moving.
- Review queue
Records the sync is not sure about land in a screen a person can read, correct and release.
- Scoped credentials
One credential per connection, limited to the objects it needs, stored encrypted, in your account.
For the team
- Slack or email notifications
The alerts go to a named person, not a channel nobody reads. You choose Slack, email, WhatsApp or all three.
- A runbook
One document per integration: what it does, what each alert means, and what to do in the first ten minutes.
- Training
A live session with the people who will use the review queue, recorded for whoever joins later.
- Handover
Admin access, billing and code sit in accounts in your name from day one. If we leave, it keeps running.
- Sixty days of hypercare
The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.
- A monthly report
Runs, records synced, exceptions handled, and what changed. Plain language, one page.
Security and your data
Where the data goes, and who holds the keys.
- Accounts
- Every platform account is created in your name. We work through managed access you can revoke.
- Credentials
- Stored encrypted in the orchestration layer. Scoped per connection. Rotated on handover.
- Data in transit
- TLS everywhere. Webhooks verified by signature before anything is processed.
- Data at rest
- Only what the sync needs. No copies of your customer data on our machines.
- AI steps
- Where an integration uses a model, it is through a business API that does not train on your data.
- Retention
- Run logs kept 90 days by default, adjustable. Payloads redacted of card and ID numbers.
- Agreements
- DPA and NDA on request. Regional rules covered in our privacy policy.
Keys and sensitive data
How API keys, tokens and personal data are handled.
- Keys live in a vault, never in code
API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.
- One credential per connection
Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.
- Service accounts, not personal logins
Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.
- Two-factor on every account
Every platform account we set up has two-factor authentication on, with recovery codes handed to you, not kept by us.
- Rotation on handover and on request
Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.
- Secrets never reach the logs
Audit logs redact tokens, card numbers, government IDs and anything you flag as sensitive before a line is written.
- Webhooks verified before processing
Inbound calls are checked against the sending tool's signature. Unsigned or stale payloads are dropped and counted.
- Access you can see and revoke
Our access is through managed roles in your accounts. You can list it, limit it, and remove it in one click without touching the build.
Engineering decisions
Decided before the first workflow is written.
- Rate limits and backoff
Every API has a ceiling. Calls are batched, queued and retried with increasing delays so a busy hour does not become a failed one.
- Backfill and pagination
The first run has to load history, not just new events. Backfills page through the source in order, resume after interruption, and never double-write.
- Out-of-order and duplicate events
Webhooks arrive twice and out of sequence. Each event carries a version or timestamp, and older versions never overwrite newer state.
- Schema changes
A renamed field or a new dropdown value is the most common silent failure. Payloads are validated against a contract, and a mismatch stops the run and raises a flag.
- Time zones, currencies, units
Dates are stored in UTC and shown local. Money carries its currency. Quantities carry their unit. Conversions happen once, in the map step.
- Sandbox first
Builds run against sandbox or test accounts with seeded data before they touch production. Go-live is a switch, not a rewrite.
- Versioned and reversible
Workflows and code are version-controlled. A release can be rolled back in minutes without losing the records processed since.
- API deprecations watched
Tools retire API versions on a schedule. We track the dates for every connection in the runbook and upgrade before the cut-off.
- Cost per run known
Each workflow has a cost per execution, including any model calls, logged alongside the run. You see the bill before it arrives.
- Metrics, not just errors
Runs per hour, records in and out, exception rate and latency are charted. Trends show a problem before an alert does.
Proof
Where we have done this.
- Customer story
Sales channel inventory sync
SmartSuite as the product source of truth with Make pushing to Shopify, eBay and Chrono24. 80% less update time, zero mismatches in 90 days, launches twice as fast.
Read the story - Customer story
Internal operations tool replacing SmartSuite
Quotations, brands and architects first ran in SmartSuite with Make reminders, then moved to a custom tool with the SmartSuite data migrated across.
Read the story
The offer
Hire SBD to connect SmartSuite and Make.
A fixed scope, agreed in a discovery call, and live in three to five business days. Accounts in your name. The engineers who built it on call for sixty days after.
- ScopeOne call to agree the flows, the fields and the owner. Written up the same day.
- Build4 workflows, the data map above, validation, upserts, retries and reconciliation.
- Go-liveSandbox first, then a switch. Day three to five from scope for most pairs; longer only if a tool needs approval, such as WhatsApp templates.
- HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
- AfterSixty days of hypercare, then a care plan or run it yourself.
Questions
What people ask about this pair.
Which SmartSuite triggers does Make offer?
The Make SmartSuite app has Watch New Records and Watch Updated Records triggers, plus actions to create, update, upsert, bulk create, bulk update and search records, and a Make an API Call module for anything else. We use upsert and bulk modules to keep request counts down.
How do we keep Make costs predictable?
Make bills in credits used by module actions, so a scenario that does less per run costs less. We filter early, batch where SmartSuite allows it, and avoid scenarios that touch records which have not changed. That also protects the SmartSuite API quota.
When should we leave SmartSuite?
When the workspace has become the business: many users, permissions that must be enforced rather than hidden, and logic spread across automations. The quotation client moved to a custom tool for that reason. Until then, SmartSuite with Make is quicker and cheaper. Workflow automation starts from $1,500.
Related
-
Shopify and eBay
One source of truth for stock, so the same unit is never sold twice on two channels.
-
Shopify and Airtable
Not a one-way order dump. A synced operational base that survives refunds, partial fulfilment and edits.
-
Airtable and Retool
Airtable is a good database and a limited interface. Retool fixes the second half.
- Solution
Inventory sync
Every workflow we automate for this kind of team.
SmartSuite and Make
Change it once in SmartSuite. Let Make tell everyone else.
Products pushed to every channel, quotes filed with their history, and reminders sent to the owner, all inside your SmartSuite API quota, built in three to five business days.
Start with a discovery call