Make · Zapier integration (no-code)
Connect Bizgo to a workflow automation tool and send messages without writing code. Events from Google Sheets, Typeform, a CRM, or a commerce platform can trigger a Bizgo API call.
Make and Zapier have official Bizgo apps, so you only pick the Bizgo action. Other tools such as n8n call the API over plain HTTP.
Get your integration keys first
Whichever tool you use, you need the API key and secret key issued under Developer tools > Key management. → Issue and manage API keys
Start the integration in the console
Go to Bizgo > Developer tools > Make/Zapier integration and connect Bizgo to the services you already use.
1. Pick the automation tool
Choose your tool on the Make/Zapier integration screen. You can send Kakao Alimtalk, Kakao Brand Message, and SMS/LMS/MMS.
- Make — Click Start integration and add the Bizgo app in Make.
- Zapier — Click Apply for access to request it.

2. Enter the integration keys
When you connect the Bizgo app in your automation tool, enter the API key and the secret key. Click Check my integration keys to look them up again.

3. Build a scenario and send
Pick a trigger (a new row in Google Sheets, for example) and connect the Bizgo send action. Map sheet columns onto message variables to vary the content per recipient. Click Send scenario to start from a sample.
Once the scenario is active, every trigger sends a message, and the results appear under Statistics/History > Send history.

Before you connect
- Running or activating a scenario sends real messages and incurs charges. Send to your own number while testing.
- Alimtalk only appears in the automation tool once the Kakao channel is registered and the template is approved.
- Bizgo charges no integration fee, but Make and Zapier bill for task runs under their own pricing.
Make lets you search for the Bizgo app in its marketplace and drop it straight into a scenario; Zapier connects the Bizgo action to a Zap. Neither needs HTTP setup — the unified key is enough.
Overview
Message send automation means setting things up so that a message is sent automatically, with no human involvement, when a particular event occurs.
Automating repetitive send work raises your operational efficiency and reduces mistakes.
Common use cases
- Send an informational SMS/LMS/MMS to a customer automatically when a row is added to Google Sheets
- Send a notification message when an order or shipping status changes
- Send announcement messages repeatedly from a prepared recipient list

When an event occurs in your data source, the automation tool detects it, calls the Bizgo API, and sends the message over the channel you specified.
Choose a tool

Build automation scenarios by clicking, no code required. Connecting external services such as Google Sheets is straightforward.

Open source. Handles complex conditional branching and can be self-hosted.

SaaS based. Connect to thousands of apps instantly with nothing to install.
Shared prerequisites
Whichever tool you use, prepare the following before you integrate.
- Create a Bizgo account and a team space.
- Register the sender number and sender information for the message channel you will use.
- Issue a Bizgo V2 API key and register the IP of your automation tool's server in the IP ACL.
- Organize the trigger data you will use for sending. For example: recipient number, name, order number, shipping status.
API key security
Store your API key using each tool's credentials, secret, or environment variable feature.
Never expose it directly in a scenario body or in a shared document.
The send flow
- An event occurs — a trigger fires in an external service (Google Sheets, Typeform, Shopify, and so on)
- Data is collected — the automation tool collects trigger data such as the recipient number and variable values
- The API is called — the HTTP request step calls the Bizgo send API
- The result is handled — you check the Bizgo response code and follow up according to success or failure
Make
Build a flow yourself in which entering data in a Google Form makes Make detect the new row in Google Sheets and send a message automatically through the Bizgo API.
Google Form submitted → Row added to Google Sheets → Make detects it → Bizgo API call → Message sent
Prerequisites
| Item | Notes |
|---|---|
| Make account | Sign up at make.com |
| Google account | For Google Form and Sheets |
| Bizgo unified API key | Issue it in Integration management |
| Sender number | You must complete sender number registration |
| Kakao channel and template | Only for Alimtalk. Complete the Kakao channel connection and get the template approved |
Step 1: Set up a Google Form
Create a Google Form to collect recipient information, and connect the responses to Google Sheets automatically.
- Sign in with your Google account.

- Go to the Google Form creation page.

- Add the items you need — phone number, message text, and so on — then create and publish the Google Form. If you send Alimtalk, add a question for each template variable (for example, name and shipping detail).

- On the Responses tab, choose Link to Sheets.

- Confirm that the response data is recorded in Google Sheets automatically.

Step 2: Create a Make scenario
In Make, set Google Sheets as the trigger so that it detects each new row.
- Sign in to Make and create a new scenario.

- From the trigger module list, choose Google Sheets.

- Choose Watch New Rows as the action.

- Under Connection, sign in with your Google account and grant the permissions.

- Choose the spreadsheet ID and sheet name you connected in step 1.

- Click Save and choose All as the point to start watching from. If the sheet already has responses, read the start-point note in Step 4 first.

Step 3: Connect the Bizgo API
Add an HTTP module to the right of the Google Sheets module to call the Bizgo send API.
- Add an HTTP module to the right of the Google Sheets module.

- Choose Make a request as the action.

- Set Authentication type to API Key.

- Click Add under Credentials and enter your Bizgo unified API key.

- Set the URL and Method.
| Item | Value |
|---|---|
| Method | POST |
| URL | https://mars.ibapi.kr/api/comm/v1/send/omni |

- Set Body Content type to
application/json.

- Choose Specification → Generate.

Up to here, SMS and Alimtalk are the same. In Step 4, pick the tab for the channel you send on and continue.
Run Generate again when you switch channels
Make fixes the input fields to the structure of the Sample JSON at the moment you run Generate. When you switch channels, start again from step 7, Specification → Generate.
Step 4: Channel input and test send
Pick the tab for your channel. Each tab continues from entering Sample data in the Generate dialog you opened in Step 3 through to a test send.
Message input
- Enter the JSON below in Sample data and click Generate. A short message of up to 90 bytes uses the
smsobject.

{
"messageFlow": [
{
"sms": {
"from": "{{CALLER_NUMBER}}",
"text": "Test message"
}
}
],
"destinations": [
{
"to": "{{PHONE_NUMBER}}"
}
]
}
- Click Add item at the bottom of Message flow.

- Enter your registered sender number in the
fromfield.

- For the
textfield, choose the message text column from Google Sheets.

- For the
tofield under Destinations, choose the phone number column from Google Sheets.

- Click Save to save it.

To send an LMS
A long message over 90 bytes. LMS uses the mms object; sent without an image fileKey, it goes out as an LMS.
{
"messageFlow": [
{
"mms": {
"from": "{{CALLER_NUMBER}}",
"title": "Notice",
"text": "Long test message"
}
}
],
"destinations": [
{
"to": "{{PHONE_NUMBER}}"
}
]
}
| Field | Map to |
|---|---|
mms.from | Your registered sender number |
mms.title | Title (optional, up to 40 bytes) |
mms.text | The message text column in Sheets (up to 2,000 bytes) |
to | The phone number column in Sheets |
The input order is the same as above. Put this JSON into Sample data and run Generate, then fill in from, title, and text under mms, choose the phone number column for to, and save.
Test send
- Enter test data in the Google Form and submit it.

- Confirm that a row was added to Google Sheets.

Check the start point before the first run
If you chose All as the start point in Step 2, the first run also sends to rows already in the sheet. To avoid sending to existing respondents, right-click the Google Sheets module → Choose where to start → Choose manually and pick the most recent row. Sending then starts from the rows added after it.
- Run the Make scenario.

- Check whether the send succeeded.

- Confirm that the message arrives on a real device.

Troubleshooting
ACL error (A403)
A Bizgo unified API key only allows requests from registered IPs. If you see an error like the one below, copy the IP address from the response and register it in the ACL in Issue and manage API keys.

{
"common": {
"authCode": "A403",
"authResult": "NOT_PERMISSION ACL Not Allowed. Please register: '35.170.163.230'"
}
}
Zapier
Use Zapier's Webhooks by Zapier action to map trigger data into a Bizgo message send request.
The integration flow
- Create a Zap and choose a trigger app. For example: Typeform, Google Sheets, Shopify
- Choose Webhooks by Zapier as the Action app.
- Choose Custom Request as the Action Event.
- Configure URL, Method, Headers, and Data.
- Map the trigger data into the JSON body.
- Test it, then turn the Zap on.
Request settings
| Item | Value |
|---|---|
| Method | POST |
| URL | https://mars.ibapi.kr/api/comm/v1/send/omni |
| Authorization | ApiKey YOUR_API_KEY |
| Content-Type | application/json |
| Data Pass-Through | false |
Data example
{
"destinations": [
{
"to": "{{phone}}",
"replaceWords": {
"name": "{{name}}"
}
}
],
"messageFlow": [
{
"sms": {
"from": "0200000000",
"text": "#{name}, your request has been received."
}
}
]
}
Using n8n and other tools
Tools without an official Bizgo app call the API from an HTTP request node. The example below uses n8n.
Build a flow yourself in which entering data in a Google Form makes n8n detect the new row in Google Sheets and send a message automatically through the Bizgo API.
Google Form submitted → Row added to Google Sheets → n8n detects it → Bizgo API call → Message sent
Prerequisites
| Item | Notes |
|---|---|
| n8n account | Sign up at n8n.io |
| Google account | For Google Form and Sheets |
| Bizgo unified API key | Issue it in Issue and manage API keys |
| Sender number | You must complete sender number registration |
Step 1: Set up a Google Form
Create a Google Form to collect recipient information, and connect the responses to Google Sheets automatically.
- Go to the Google Form creation page.

- Add the items you need — phone number, message text, and so on — and create the Google Form.

- Publish the form you created.

- Go to the Responses tab.

- Choose Link to Sheets.

- Confirm that the response data is recorded in Google Sheets automatically. From now on, n8n detects each row added to this sheet.

Step 2: Connect the Google Sheets trigger
In your n8n workflow, set Google Sheets as the trigger and connect your Google account.
- Sign in to n8n and create a new workflow.

- Choose On app event → Google Sheets.


- Set Event to Row Added.

- Start connecting the Google credential.

- Go to the Google Cloud Console.

- Create a new project.


- Enter a project name and click Create.

- Choose APIs & Services → Enabled APIs & services.

- Click Enable APIs and services.

- Search for Google Drive API and enable it.

- Search for Google Sheets API and enable it.


- Choose OAuth consent screen.

- Click Clients → Create client.

- Set Application type to Web application and enter a name.

- Click Authorized redirect URIs → Add URL.

- Copy the OAuth Redirect URL from n8n and paste it in.


- Check the Client ID and Client secret that were created.

- Click Audience → Test Users → Add users.

- Enter the Google account you will use and click Save.

- Enter the Client ID and Client secret in the credential fields in n8n.

- Choose Sign in with Google.

- Click Continue in the sign-in popup.

- Review the permission request and click Continue.

- Confirm that the Google account connected successfully.

Step 3: Configure the Google Sheets integration
Set the spreadsheet the trigger runs against and the polling interval, then fetch test data.
- Add a column to Google Sheets to store the delivery result.

- Set Poll Times to Custom and enter the value below.

*/1 * * * * *
- Choose Document and Sheet, and set Trigger On to Row Added.

- Choose Add option → Data Location on Sheet and configure it as follows.

| Item | Value |
|---|---|
| Range Definition | Specify Range (Rows) |
| Header Row | 1 |
| First Data Row | 2 |
- Enter test data in the Google Form and submit it.

- Click Fetch Test Event.

- Check the Google Sheets data in OUTPUT.

Step 4: Set up conditional branching (Flow)
Add an if condition so that you send only when the delivery result column is empty.
- Add Flow → if after the Google Sheets node.


- From INPUT, drag the delivery result field onto the if condition.

- Set the condition to is empty.

Step 5: Connect the Bizgo API
Add an HTTP Request node on the if true path to call the Bizgo send API.
- On the if true path, add Action in an app → HTTP Request.


- Configure the basic HTTP Request items.

| Item | Value |
|---|---|
| Method | POST |
| URL | https://mars.ibapi.kr/api/comm/v1/send/omni |
| Authorization | None |
- Turn on Send Headers and enter
ApiKey {your Bizgo unified API key}in theAuthorizationheader.

- Turn on Send Body, choose Using JSON, then enter the JSON below.

{
"messageFlow": [
{
"sms": {
"from": "{{CALLER_NUMBER}}",
"text": "Test message"
}
}
],
"destinations": [
{
"to": "{{PHONE_NUMBER}}"
}
]
}
- From the INPUT fields, drag the phone number and message text data from Google Sheets to map them.

- Click Execute step to run a test send.

Step 6: Store the delivery result
Record the delivery result in Google Sheets to prevent duplicate sends.
- Add Action in an app → Google Sheets to the right of the HTTP Request node.


- Choose Update row in sheet.

- Connect with your Google account.


- Configure Parameters as follows.

| Item | Value |
|---|---|
| Resource | Sheet Within Document |
| Operation | Update Row |
- Set Mapping Column Mode to Map Each Column Manually and set match on to Timestamp.

- Drag the Timestamp and the HTTP Request result values to map them.

- Choose Add option → Data Location on Sheet.

- Click Execute step.

- Check the stored result in OUTPUT.

Step 7: Confirm the final run
- Check the workflow run history under Executions at the top right.

Troubleshooting
ACL error (A403)
A Bizgo unified API key only allows requests from registered IPs. If you see an error like the one below, copy the IP address from the response and register it in the ACL in Issue and manage API keys.
{
"common": {
"authCode": "A403",
"authResult": "NOT_PERMISSION ACL Not Allowed. Please register: '35.170.163.230'"
}
}
Next
- Checking results → Check web and system send results
- API specification → API reference






