STEP 1
Connect Arpoone and SOLAPI
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Arpoone and SOLAPI Integration
Keep Arpoone and SOLAPI in sync by integrating their events and actions. When communication events happen in Arpoone, update the SOLAPI automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Arpoone and SOLAPI
Detailed info you need to know about Arpoone and SOLAPI integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Arpoone to SOLAPI
Set up your Arpoone and SOLAPI integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Arpoone and SOLAPI nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Arpoone and SOLAPI. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Arpoone and SOLAPI work in WEXTL?
WEXTL exposes actions and triggers for Arpoone and SOLAPI that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
SOLAPI triggersArpoone actions
SOLAPI modules
- Accept a Kakao Channel Group InvitationAccepts an invitation to join a Kakao channel group.
- Add a Blocked NumberAdds a phone number to the opt-out list or edits an existing entry.
- Add a Kakao ChannelLinks a Kakao channel to the account using a verification token.
- Add a Kakao Channel ServiceConnects a Kakao channel to a service using a verification token.
- Add Blocked Numbers in BulkAdds many phone numbers to an opt-out group at once.
- Add Messages to a GroupAdds messages to a pending message group.
- Cancel a Kakao Channel Group InvitationCancels a pending Kakao channel group invitation.
- Cancel an Alimtalk Template ReviewWithdraws an Alimtalk template from Kakao review.
- Cancel a Scheduled Message GroupCancels the scheduled send of a message group.
- Check a Sender NumberReturns whether a phone number is already registered as a sender number.
- Check CRM Segment MembershipReturns whether a CRM record currently matches a segment.
- Complete a CRM ActivityMarks a CRM activity as completed.
- Copy a Brand Message TemplateCopies a Brand Message template to another Kakao channel.
- Create a Brand Message TemplateCreates a Kakao Brand Message template.
- Create a CRM ActivityLogs a call, email, meeting, note, task, or message against a CRM record.
- Create a CRM EntityCreates a CRM entity.
- Create a CRM PropertyAdds a property to a CRM entity.
- Create a CRM RecordCreates a record in a CRM entity.
- Create a CRM RelationshipLinks two CRM records with a relationship type.
- Create a CRM Relationship TypeCreates a relationship type between two CRM entities.
- Create a Kakao Channel GroupCreates a Kakao channel group from existing channels.
- Create a Message GroupCreates an empty message group to fill and send later.
- Create an Alimtalk TemplateCreates a Kakao Alimtalk template for review.
- Create CRM Properties in BulkAdds several properties to CRM entities at once.
- Create CRM Relationships in BulkLinks many CRM records to target records at once.
- Create or Update a Block GroupCreates an opt-out group or updates an existing one.
- Decline a Kakao Channel Group InvitationDeclines an invitation to join a Kakao channel group.
- Delete a Brand Message TemplateDeletes a Kakao Brand Message template.
- Delete a CRM ActivityPermanently deletes a CRM activity.
- Delete a CRM EntityMoves a CRM entity and its records to the trash.
- Delete a CRM PropertyDeletes a CRM property and its stored values.
- Delete a CRM RecordMoves a CRM record to the trash.
- Delete a CRM RelationshipDeletes a CRM relationship.
- Delete a CRM Relationship TypeDeletes a CRM relationship type.
- Delete a CRM SegmentDeletes a CRM segment.
- Delete a FileDeletes a stored file.
- Delete a Kakao ChannelUnlinks a Kakao channel from the account.
- Delete a Kakao Channel GroupDeletes a Kakao channel group.
- Delete a Message GroupDeletes a message group.
- Delete an Alimtalk TemplateDeletes an Alimtalk template.
- Delete a Sender NumberDeletes a registered sender number.
- Delete a Sender Number AliasDeletes the alias of a sender number.
- Delete CRM Records in BulkMoves many CRM records to the trash or deletes them permanently.
- Find Duplicate CRM RecordsRetrieves groups of CRM records that share the same values.
- Get Account WarningsReturns the warnings recorded against the account.
- Get a CRM ActivityReturns a single CRM activity.
- Get a CRM EntityReturns a single CRM entity with its settings.
- Get a CRM PropertyReturns a single CRM property.
- Get a CRM RecordReturns a single CRM record with its values, tags, and files.
- Get a CRM Record Export StatusReturns the status and download link of a CRM record export.
Arpoone modules
- Create a RecipientCreates a Recipient.
- Make an API CallPerforms an arbitrary authorized API call.
- Send an EmailSends an Email.
- Send an SMSSends an SMS.
- Update a RecipientUpdates a Recipient with new field values.
Frequently asked questions
Common questions about connecting Arpoone and SOLAPI.
Connect your Arpoone and SOLAPI accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when SOLAPI's "Watch Group Reports" fires, WEXTL can "Create a Recipient" in Arpoone. Arpoone has 5 actions (including Create a Recipient, Make an API Call, and Send an Email); SOLAPI has 139 actions (including Accept a Kakao Channel Group Invitation, Add a Blocked Number, and Add a Kakao Channel). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Arpoone-to-SOLAPI automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Arpoone (or SOLAPI) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Arpoone + SOLAPI automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Arpoone and SOLAPI integration.
- Arpoone and SOLAPI integration source code, module specs and credentials implementation.
- Our Arpoone and SOLAPI integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Arpoone and SOLAPI — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Arpoone integration information
- SOLAPI integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library