SOLAPI

SOLAPI

· #351 most-used

Send KakaoTalk, SMS, and RCS messages and automate CRM workflows across Korea's top channels

CRMSalesMarketingCommunicationAutomationEmail Marketing

SOLAPI is South Korea's leading cloud messaging API platform — combining SMS, LMS, MMS, KakaoTalk AlimTalk and FriendTalk, and RCS Rich Communication Services in a single API, with a built-in CRM for tracking contacts, events, and customer records. Connect SOLAPI to Actionist and your agents can send any message type across any Korean channel, react to commerce events and delivery reports within about a minute, maintain CRM records and activities automatically, and orchestrate full customer communication sequences — without anyone touching the SOLAPI console.

Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of sending individual KakaoTalk and SMS messages, logging CRM activities after every send, and monitoring bulk delivery reports by hand.

Schedule

What your SOLAPI agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
TueThu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

SOLAPI × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
4Apps spanned
~29 hrsSaved / week
6Personas served
For sales
Featured3 apps

New lead lands in CRM and receives first-touch AlimTalk in seconds

When a new lead row appears in the Google Sheets pipeline tracker, the agent creates a SOLAPI CRM record, adds them to the address book, sends a personalised first-touch KakaoTalk AlimTalk using the welcome template, logs the send as a CRM activity, and alerts the #sales-inbound Slack channel — all before a rep sees the notification.

~8 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a new lead row is added to the sales pipeline Google Sheet
Result
Create CRM record for the new lead in SOLAPIAdd contact to SOLAPI address book with opt-in tagSend Kakao AlimTalk first-touch message using welcome templateAdd CRM record activity logging the first-touch sendPost new lead notification to #sales-inbound Slack channel
The win
Saved per run
15 min
Runs / week
~30×
Every new lead is contacted within about a minute of entering the pipeline
Driven bySales Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    25 min / week
    Manual lead response and CRM entry

    Reps manually log new leads in the CRM, draft and send individual welcome messages, and often respond hours after the lead arrives — by which time intent has cooled.

    Sales Agent
    0 min
    Agent sends personalised AlimTalk to every new lead in seconds

    When a new lead enters the pipeline, the agent creates a CRM record and sends the welcome AlimTalk within about a minute — the prospect hears from the company before the rep sees the notification.

  • Marketing
    90 min / week
    Manual segment export and campaign send

    The marketing team exports customer lists from the CRM, imports them into SOLAPI, builds the segment manually, and sends the campaign — a process that takes hours and introduces data-freshness lag.

    Marketing Agent
    0 min
    Agent segments and sends campaigns based on CRM event data

    The agent reads CRM event summaries to build precise segments and sends the right KakaoTalk brand message to each segment automatically — no manual list exports or platform switching needed.

  • Customer Support
    30 min / week
    Manual transactional message dispatch

    Support agents manually send confirmation messages after purchases and resolutions — often delayed, inconsistently worded, and dependent on whoever is on shift at the time.

    Customer Support Agent
    0 min
    Agent sends order confirmations and post-sale messages automatically

    Every purchase, refund, or support resolution triggers the right AlimTalk template within about a minute. The customer is never left wondering whether their order was received.

  • Human Resources
    20 min / week
    Manual onboarding message preparation

    HR manually prepares welcome messages for each new hire, copies in the right template, sends them individually, and manually creates follow-up reminders in the calendar — 20 minutes per hire.

    Human Resources Agent
    0 min
    Agent sends onboarding AlimTalks and schedules CRM check-ins on Day 1

    When a new hire row appears in the roster, the agent sends the Day 1 welcome AlimTalk and schedules check-in events automatically — the new hire is welcomed before HR's morning meeting.

  • Finance
    35 min / week
    Manual invoice chasing by email and call

    Finance staff manually identify overdue invoices, draft individual chase messages, and track whether they have been sent in a spreadsheet — a repetitive process that slips when the team is busy.

    Finance Agent
    0 min
    Agent sends RCS and AlimTalk reminders to every overdue invoice automatically

    When an invoice goes overdue, the agent immediately sends a rich RCS payment card with a 'Pay Now' button and logs the reminder event — no manual chase required for standard overdue accounts.

  • Operations
    40 min / week
    Manual bulk send monitoring and retry

    The operations team manually checks the SOLAPI console after each bulk send, exports failed recipients, and re-queues the retry — often discovering failures hours after the original send.

    Operations Agent
    0 min
    Agent monitors delivery rates and retries failed sends within minutes

    After every bulk send, the agent reads the group report, posts the delivery rate to Slack, and automatically retries failed recipients — the team knows send health without watching the SOLAPI dashboard.

  • Legal
    20 min / week
    Manual consent and opt-out record-keeping

    The legal team manually tracks consent events in a spreadsheet, sends opt-out acknowledgements by email, and compiles audit evidence on request — a labour-intensive process with gaps under pressure.

    Legal Agent
    0 min
    Agent logs consent confirmations and opt-outs with full audit trail

    Every consent grant and opt-out triggers an AlimTalk confirmation and a timestamped CRM activity log — legal can demonstrate per-contact notification compliance without manual records.

+ 100s of other SOLAPI automations
Average time saved
26 hrs / person / month
Calculator

Calculate what your team saves

Team size
5 people
Hourly rate
$75 / hr
Hours saved / week
13
Hours saved / year
625
Annual ROI
$46,875

Based on SOLAPI's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug SOLAPI into Actionist

Pick the connection method that suits your environment.

The fastest way to connect SOLAPI. Authorise via OAuth and the agent gains access to your messaging channels and CRM — no API keys to paste or manage.

1
Open the Apps tab

Find SOLAPI in the Apps library and click Connect. OAuth is the recommended method.

2
Authorise in SOLAPI

A SOLAPI authorisation window opens — log in with your SOLAPI account and grant Actionist permission to read and send messages and access your CRM. The handshake completes in under 10 seconds.

3
Test the connection

Actionist runs a read-only test call to confirm the connection is live. You are ready to start building agent tasks.

Actions

15 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

9 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

FAQs

Questions about SOLAPI + Actionist

How does Actionist connect to SOLAPI?
Go to the Apps tab, find SOLAPI, and click Connect. The recommended path is OAuth — Actionist opens the SOLAPI OAuth window where you authorise access with your client ID and client secret from the SOLAPI console. Actionist runs a test call to confirm the handshake before any actions execute. If you prefer a direct API key approach, you can paste your SOLAPI API key and secret from your account dashboard instead.
What permissions does the agent need on my SOLAPI account?
The agent needs read and write permissions on your SOLAPI account to send messages and access CRM data. For messaging (SMS, KakaoTalk AlimTalk, FriendTalk, RCS), write scope is required. For reading group reports, CRM records, and event summaries, read scope is required. The OAuth flow requests both scopes together. SOLAPI also requires that your account is registered for KakaoTalk channel use (AlimTalk / FriendTalk) via the SOLAPI console before those message types can be sent.
Can I send to multiple message channels (SMS, KakaoTalk, RCS) in the same workflow?
Yes. SOLAPI is designed as a multi-channel messaging hub — the same API call selects the channel (SMS, LMS, MMS, AlimTalk, FriendTalk, RCS Template, or RCS free-form). In Actionist, you can use the appropriate action for each channel in the same workflow. For example: send an AlimTalk for an order confirmation, then fall back to SMS if the recipient has not registered with KakaoTalk, all in a single agent task.
What is the difference between AlimTalk, FriendTalk (KakaoTalk), and RCS in SOLAPI?
AlimTalk is an informational message channel (order confirmations, shipping updates, appointment reminders) that is delivered inside the KakaoTalk app to users who have KakaoTalk installed. FriendTalk is a KakaoTalk channel for branded messages with images and buttons — closer to marketing messages. RCS (Rich Communication Services) replaces SMS with rich content including cards, carousels, and action buttons, delivered natively in the device SMS app without requiring a third-party app install. Each has its own approval and registration process inside the SOLAPI console.
Does SOLAPI's CRM integrate with its messaging in Actionist?
Yes. SOLAPI's CRM layer tracks customer records, properties, and events (page views, purchases, form submissions). In Actionist, the agent can create a CRM record when a new lead arrives, track an event when a purchase is made, and trigger a follow-up message sequence — all in a single workflow. The CRM and messaging APIs share the same SOLAPI account, so customer segments built from events can immediately be targeted for outbound messaging.
How do I track delivery rates for bulk message sends in Actionist?
SOLAPI group reports aggregate delivery status across a batch send — including delivered, failed, and pending counts. In Actionist, the New Group Report trigger fires within about a minute of a group send completing, allowing your agent to react automatically: write the summary to a spreadsheet, alert a Slack channel if the delivery rate drops below threshold, or trigger a resend workflow for failed recipients. The New Message Report trigger fires per individual message status update for more granular tracking.
Do KakaoTalk messages require pre-approved templates?
KakaoTalk AlimTalk and Brand Template messages require pre-approved message templates registered in the SOLAPI console and approved by Kakao. The template ID is a required parameter in the Actionist action. You cannot send freeform AlimTalk content — only approved template bodies with variable placeholders. FriendTalk (Brand Message Free Type) does not require pre-approval and allows freer content, but your KakaoTalk channel must still be registered and active in SOLAPI.
Does SOLAPI work for sending messages outside South Korea?
SOLAPI is a Korean messaging API platform, so it is most commonly used for messaging recipients in South Korea. It natively supports Korean carriers and KakaoTalk (dominant in South Korea). RCS coverage depends on carrier support in the target region. If your recipients are outside Korea, check SOLAPI's documentation for supported destination countries for SMS and LMS before building your workflow — some international routes may require additional configuration or use of a different messaging channel.