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.

Make and Zapier integration

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.

Check integration keys

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.

Send a scenario

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

Basic structure of no-code automation

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


Shared prerequisites

Whichever tool you use, prepare the following before you integrate.

  1. Create a Bizgo account and a team space.
  2. Register the sender number and sender information for the message channel you will use.
  3. Issue a Bizgo V2 API key and register the IP of your automation tool's server in the IP ACL.
  4. 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

  1. An event occurs — a trigger fires in an external service (Google Sheets, Typeform, Shopify, and so on)
  2. Data is collected — the automation tool collects trigger data such as the recipient number and variable values
  3. The API is called — the HTTP request step calls the Bizgo send API
  4. 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.

TEXT
Google Form submitted → Row added to Google Sheets → Make detects it → Bizgo API call → Message sent

Prerequisites

ItemNotes
Make accountSign up at make.com
Google accountFor Google Form and Sheets
Bizgo unified API keyIssue it in Integration management
Sender numberYou must complete sender number registration
Kakao channel and templateOnly 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.

  1. Sign in with your Google account.

Sign in with your Google account

  1. Go to the Google Form creation page.

Go to the Google Form creation page

  1. 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).

Create the Google Form

  1. On the Responses tab, choose Link to Sheets.

Connect Link to Sheets

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

Confirm the Sheets integration


Step 2: Create a Make scenario

In Make, set Google Sheets as the trigger so that it detects each new row.

  1. Sign in to Make and create a new scenario.

Create a Make scenario

  1. From the trigger module list, choose Google Sheets.

Choose the Google Sheets module

  1. Choose Watch New Rows as the action.

Choose Watch New Rows

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

Connect your Google account

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

Connect the spreadsheet

  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.

Save and choose All


Step 3: Connect the Bizgo API

Add an HTTP module to the right of the Google Sheets module to call the Bizgo send API.

  1. Add an HTTP module to the right of the Google Sheets module.

Add the HTTP module

  1. Choose Make a request as the action.

Choose Make a request

  1. Set Authentication type to API Key.

Choose API Key authentication

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

Enter the unified API key

  1. Set the URL and Method.
ItemValue
MethodPOST
URLhttps://mars.ibapi.kr/api/comm/v1/send/omni

Set the URL and Method

  1. Set Body Content type to application/json.

Set Body Content type

  1. Choose Specification → Generate.

Choose 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

  1. Enter the JSON below in Sample data and click Generate. A short message of up to 90 bytes uses the sms object.

Enter the sample JSON

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

Click Add item

  1. Enter your registered sender number in the from field.

Set the from field

  1. For the text field, choose the message text column from Google Sheets.

Map the text field

  1. For the to field under Destinations, choose the phone number column from Google Sheets.

Map the to field

  1. Click Save to save it.

Saving complete

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.

JSON
{
  "messageFlow": [
    {
      "mms": {
        "from": "{{CALLER_NUMBER}}",
        "title": "Notice",
        "text": "Long test message"
      }
    }
  ],
  "destinations": [
    {
      "to": "{{PHONE_NUMBER}}"
    }
  ]
}
FieldMap to
mms.fromYour registered sender number
mms.titleTitle (optional, up to 40 bytes)
mms.textThe message text column in Sheets (up to 2,000 bytes)
toThe 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

  1. Enter test data in the Google Form and submit it.

Submit the Google Form

  1. Confirm that a row was added to Google Sheets.

Confirm the row was added to 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.

  1. Run the Make scenario.

Run the scenario

  1. Check whether the send succeeded.

Confirm the send succeeded

  1. Confirm that the message arrives on a real device.

Confirm the message was received


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.

Check the ACL error

JSON
{
  "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

  1. Create a Zap and choose a trigger app. For example: Typeform, Google Sheets, Shopify
  2. Choose Webhooks by Zapier as the Action app.
  3. Choose Custom Request as the Action Event.
  4. Configure URL, Method, Headers, and Data.
  5. Map the trigger data into the JSON body.
  6. Test it, then turn the Zap on.

Request settings

ItemValue
MethodPOST
URLhttps://mars.ibapi.kr/api/comm/v1/send/omni
AuthorizationApiKey YOUR_API_KEY
Content-Typeapplication/json
Data Pass-Throughfalse

Data example

JSON
{
  "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.

TEXT
Google Form submitted → Row added to Google Sheets → n8n detects it → Bizgo API call → Message sent

Prerequisites

ItemNotes
n8n accountSign up at n8n.io
Google accountFor Google Form and Sheets
Bizgo unified API keyIssue it in Issue and manage API keys
Sender numberYou 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.

  1. Go to the Google Form creation page.

Go to the Google Form creation page

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

Create the Google Form

  1. Publish the form you created.

Publish the Google Form

  1. Go to the Responses tab.

Go to the Responses tab

  1. Choose Link to Sheets.

Connect Link to Sheets

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

Confirm the Sheets integration


Step 2: Connect the Google Sheets trigger

In your n8n workflow, set Google Sheets as the trigger and connect your Google account.

  1. Sign in to n8n and create a new workflow.

Create a workflow

  1. Choose On app event → Google Sheets.

Choose Google Sheets

Confirm the Google Sheets selection

  1. Set Event to Row Added.

Set Row Added

  1. Start connecting the Google credential.

Start connecting the credential

  1. Go to the Google Cloud Console.

Go to the Google Cloud Console

  1. Create a new project.

Create a project

Confirm the project creation

  1. Enter a project name and click Create.

Enter the project name

  1. Choose APIs & Services → Enabled APIs & services.

Choose APIs & Services

  1. Click Enable APIs and services.

Click Enable APIs

  1. Search for Google Drive API and enable it.

Enable the Google Drive API

  1. Search for Google Sheets API and enable it.

Enable the Google Sheets API

API enablement complete

  1. Choose OAuth consent screen.

OAuth consent screen

  1. Click Clients → Create client.

Click Create client

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

Choose Web application

  1. Click Authorized redirect URIs → Add URL.

Click Add URL

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

Copy the Redirect URL

Paste the Redirect URL

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

Check the Client ID and secret

  1. Click Audience → Test Users → Add users.

Add test users

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

Enter the Google account and save

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

Enter the n8n credential

  1. Choose Sign in with Google.

Sign in with Google

  1. Click Continue in the sign-in popup.

Continue in the sign-in popup

  1. Review the permission request and click Continue.

Continue after reviewing the permissions

  1. Confirm that the Google account connected successfully.

Confirm the successful connection


Step 3: Configure the Google Sheets integration

Set the spreadsheet the trigger runs against and the polling interval, then fetch test data.

  1. Add a column to Google Sheets to store the delivery result.

Add the delivery result column

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

Set Poll Times

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

Set Document and Sheet

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

Set Data Location

ItemValue
Range DefinitionSpecify Range (Rows)
Header Row1
First Data Row2
  1. Enter test data in the Google Form and submit it.

Enter test data

  1. Click Fetch Test Event.

Click Fetch Test Event

  1. Check the Google Sheets data in OUTPUT.

Check the OUTPUT data


Step 4: Set up conditional branching (Flow)

Add an if condition so that you send only when the delivery result column is empty.

  1. Add Flow → if after the Google Sheets node.

Add Flow if

Choose the if node

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

Drag the delivery result field

  1. Set the condition to is empty.

Set the is empty condition


Step 5: Connect the Bizgo API

Add an HTTP Request node on the if true path to call the Bizgo send API.

  1. On the if true path, add Action in an app → HTTP Request.

Add HTTP Request

Choose HTTP Request

  1. Configure the basic HTTP Request items.

Configure HTTP Request

ItemValue
MethodPOST
URLhttps://mars.ibapi.kr/api/comm/v1/send/omni
AuthorizationNone
  1. Turn on Send Headers and enter ApiKey {your Bizgo unified API key} in the Authorization header.

Configure Send Headers

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

Enter the Send Body JSON

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

Map the INPUT fields

  1. Click Execute step to run a test send.

Run Execute step


Step 6: Store the delivery result

Record the delivery result in Google Sheets to prevent duplicate sends.

  1. Add Action in an app → Google Sheets to the right of the HTTP Request node.

Add the Google Sheets node

Choose the Google Sheets node

  1. Choose Update row in sheet.

Choose Update row

  1. Connect with your Google account.

Connect your Google account

Confirm the connection

  1. Configure Parameters as follows.

Configure Parameters

ItemValue
ResourceSheet Within Document
OperationUpdate Row
  1. Set Mapping Column Mode to Map Each Column Manually and set match on to Timestamp.

Configure Mapping Column

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

Map the result values

  1. Choose Add option → Data Location on Sheet.

Add Data Location

  1. Click Execute step.

Click Execute step

  1. Check the stored result in OUTPUT.

Check the stored result in OUTPUT


Step 7: Confirm the final run

  1. Check the workflow run history under Executions at the top right.

Check the Executions run history


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.

JSON
{
  "common": {
    "authCode": "A403",
    "authResult": "NOT_PERMISSION ACL Not Allowed. Please register: '35.170.163.230'"
  }
}

Next