Bring your data in. Send events out.
Sync records from databases, REST APIs, Google Sheets, CSV files and webhooks, with AI field mapping and scheduled runs. Then connect the rest of your stack with signed event webhooks, a REST API and an MCP server.
For teams whose data lives in more than one tool, and the developers who connect them.
Why connect your tools
An integration copies records from another system into a Scratchboard entity (a table such as Customers or Orders) and keeps them up to date.
Stop re-typing data
Records from your database, sheets and other tools arrive in Scratchboard on a schedule, already in the right fields.
One place to work
Once the data is in, your team can use the same views, workflows, permissions and reports on it.
See it before it lands
Preview the first rows before a full sync and get warned when the source's columns change.
How it works
A guided wizard, from connection to first sync.
- 1
Connect a source
Choose a database, API, Google Sheet, CSV file or webhook, enter the details, and test the connection.
- 2
Map the fields
Pick the tables to sync. The AI maps each column to a field, and you adjust, add transforms or create new fields.
- 3
Schedule and monitor
Set how often it runs, preview 10 rows, then run it. Every sync is logged, with errors you can fix and retry.
Try it: map a source with AI
Pick a source and press AI auto-map to see the kind of suggestions you get.
1. Pick a source
2. Map the fields
Sheet “Leads 2026”
text
Not mapped
Full Name
text
Not mapped
Deal Value
text
Not mapped
Stage
text
Not mapped
Signed up
text
Not mapped
Sample data. In the app, the AI reads the real columns from your source and suggests a target field for each one.
See it in a real business
A short walkthrough that follows one business through the problem and the fix.
Data & integrations 2:31
Import, sync, webhooks and API: one place that stays in step
Peak Fitness, a gym with members in three places
Members in a spreadsheet, bookings in another system's database, and an accountant who wanted a list every month. Here is how they made it one.
- Spreadsheet import with column matching and duplicate handling
- An hourly database sync with run logs and schema-change alerts
- Signed webhooks with retries and replay
- A read-only API key, and an Excel export saved as a preset
Chapters (9)· jump straight to a part
Data in
Five ways to bring records into Scratchboard.
Databases
PostgreSQL, MySQL and SQL Server. Paste a connection string or fill in the form, then test the connection.
REST APIs
Paste a cURL command or a sample response to fill in the URL, auth and pagination for you.
Google Sheets
Sign in with Google and pick a spreadsheet, or use a service account.
CSV files
Point at a CSV file by URL and pull it on a schedule.
Inbound webhooks
Get a URL that other tools can POST to. Send one test request and the fields are detected for you.
Data out
Let other systems and AI assistants react to your data.
Event webhooks
Subscribe any URL to events such as a record being created or updated, filtered by entity. Each delivery is signed with a secret, logged, and can be retried.
API connections
Save an outside API once, with its auth, headers and retries, and call it from any workflow step or record button.
REST API and API keys
Read and write every entity over the REST API. Keys can be limited to specific permissions and set to expire.
MCP server
Connect Claude, ChatGPT and other MCP clients (apps that speak the Model Context Protocol) so AI assistants can work with your data.
Email, SMS and WhatsApp
Plug in your own providers (SMTP, SendGrid, Brevo, Amazon SES, Twilio, MSG91, WhatsApp Cloud API) and send from workflows with templates.
Key capabilities
What keeps a sync accurate and easy to look after.
AI field mapping
The AI suggests a target field for every source column, with a confidence score. Create missing fields in one click.
Transforms
Convert types, map values (“won” → “Closed Won”), split or combine columns, set defaults, or build a value from a template.
Scheduled sync
Run manually, every 15 minutes, hourly, daily or on your own cron schedule, with full or incremental syncs.
Two-way sync
Push changes made in Scratchboard back to the source, and choose which side wins when both changed.
Schema drift checks
See columns that were added, removed or changed type at the source, then jump straight to the mappings.
Preview before syncing
Test with 10 rows to see each source record next to the record it would create. Nothing is saved.
Run history and fixes
Every sync is logged with counts and errors. Common errors come with a suggested fix and a Retry button.
Secure inbound webhooks
Verify HMAC signatures, restrict senders to an IP allowlist, and drop duplicate deliveries automatically.
For developers
- REST API at https://api.scratchboard.cloud/v1 with Bearer API keys, for every entity: list, get, create, update, delete and related records.
- Event webhooks signed with a per-endpoint secret you can roll, with a delivery log and one-click retry.
- A hosted MCP server at https://mcp.scratchboard.cloud/mcp for Claude, ChatGPT and other MCP clients.
Frequently asked questions
Short answers to what buyers usually ask.
Which systems can I connect?
Data integrations support PostgreSQL, MySQL and SQL Server databases, REST APIs, Google Sheets, CSV files by URL, and inbound webhooks. For anything else, use the REST API, event webhooks, API connections inside workflows, or the MCP server.
Do I need a developer to set up a sync?
Usually not. A six-step wizard walks you through connecting, choosing tables, mapping fields (the AI does most of it), and setting a schedule. You can preview 10 rows before running the first full sync.
How often does data sync?
It depends on your plan: hourly on Starter, every 5 min on Pro and custom on Enterprise. You can also run a sync by hand at any time, and inbound webhooks arrive as they are sent.
Can Scratchboard write changes back to my database or API?
Yes, with two-way sync (not included on Starter, included on Pro and included on Enterprise). You pick a conflict rule: the source wins, Scratchboard wins, the newest change wins, or skip.
How are credentials and webhooks protected?
Passwords and tokens are entered in masked fields and never shown back in full. Outgoing event webhooks are signed so the receiver can verify them, and inbound webhooks can require a signature and an IP allowlist. API keys are shown once at creation and can be scoped and set to expire.
Related features
Scratchboard features that work together with this one.
Developers
REST API reference, webhooks and quick starts.
MCP server
Connect Claude, ChatGPT and other AI clients.
Workflows
Act on synced data automatically.
Entity engine
The data model your sources map into.
Permissions
Decide who sees synced data.
Reports
Report across data from every source.
Vector search
Search synced records by meaning.
Pricing
Integration limits per plan. Every plan starts with a 7-day free trial.
Connect your first data source
Every plan starts with a 7-day free trial. Connect a sheet or database and see your records in Scratchboard in minutes.