Skip to content
Making the Complex Simple
Making the Complex Simple
Making the Complex Simple - Research
Data map
CODA & Swipe One - Web hooks
Share
Explore

CODA & Swipe One - Web hooks

Complete Guide: Connecting Coda to Swipe One via Make.com

This guide explains how to send data from a Coda form to Swipe One CRM using a free Coda plan. The process uses Make.com as a "middleman" to correctly format and forward the data.
The Data Flow:
Coda Button Click
→
Make.com Webhook
→
Swipe One CRM
⁠

Part 1: Coda Setup

Goal: Create a button in your Coda table that sends contact data to a Make.com webhook.
Install the Correct Pack: Because the Coda Free plan doesn't have a built-in webhook action, you must use a community Pack.
Install the "Make.com w/ Payload" Pack by Eber Domingos. This Pack is allowed to connect to Make.com URLs.
Create a Button Column:
In your Coda table, add a new column and set its type to Button.
Configure the Button Action:
Click the button options and choose the action from the Pack you just installed (e.g.,
Send to Make.com with Payload
).
You will see two main fields:
Webhook URL: Paste your unique webhook URL from Make.com here (see Part 2, Step 1).
Payload / JSON Data: Click the
f
icon to turn this into a formula field.
Add the Coda Formula:
Paste the following formula into the "Payload" field. This formula gathers all the data from the row and includes your "tag" workaround for the newsletter.
Object(
"Full Name", thisRow.[First & Last Name],
"Email", thisRow.[Email address],
"Job Title", thisRow.Title,
"Company Name", thisRow.[Company Name],
"Phone Number", thisRow.[Contact number],
"Website", thisRow.[Company URL],
"Tag", If(thisRow.Newsletter, "Book Updates Newsletter", "")
)

⁠

Part 2: Make.com Setup

Goal: Create a scenario that catches the data from Coda and sends it to Swipe One in the correct format.
Module 1: The Trigger (Webhook)
Create a new scenario in Make.com.
For the first module, select Webhooks, then choose the trigger Custom webhook.
Click Add, name your webhook, and copy the unique URL it provides. This is the URL you paste into your Coda button settings.
Module 2: The Action (HTTP Request)
Add a second module to your scenario. Select the HTTP app, then choose the action Make a request.
This is where we solved the biggest problems. Configure it with these exact settings:
URL: Your Swipe One webhook URL (
https://integrations-api.swipeone.com/...
).
Method:
POST
.
Body type:
Application/x-www-form-urlencoded
. This is critical. Do not use
Raw (JSON)
.
Fields: Add an item for each piece of data you want to send. The Key must be the
camelCase
name Swipe One expects, and the Value is the data mapped from your Coda webhook.
Data map
Key
Value (Mapped from Coda Webhook)
fullName
{{1.Full Name}}
email
{{1.Email}}
jobTitle
{{1.Job Title}}
companyName
{{1.Company Name}}
phoneNumber
{{1.Phone Number}}
website
{{1.Website}}
tags
{{1.Tag}}
There are no rows in this table
⁠
Save and Activate: Save your scenario and turn it on.
Tip for data map in
make.com
⁠
: Send data to
make.com
⁠
and it will show the fields to align in vales to the Keys you put in.
⁠

Key Lessons Learned

"Undeclared Hostname" Error: This error means a Coda Pack is locked to a specific service (like
make.com
). The solution was to use the Make.com Pack and send the data there first.
Form Data vs. JSON: The final
Validation failed
error from Swipe One was solved by changing the Make.com HTTP module's Body typefrom
Raw (JSON)
to
Application/x-www-form-urlencoded
.
Field Naming: The receiving service (Swipe One) dictates the field names. We had to change keys like "Full Name" to
fullName
in the final HTTP request for it to be accepted.
You've built a robust and reliable integration. Congratulations again on your great work
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.