Go4Clients
MessagingConnect AI agents to Go4Clients, a multichannel campaign platform for SMS, voice, and email. Agents send messages and calls, run drip and verification campaigns, manage contacts and blacklists, and pull channel analytics so multichannel outreach runs from a single flow.
What This Integration Enables
Go4Clients is a multichannel campaign platform out of Weston, Florida, with a parent company operating across Latin America, and one credential pair covers a surprising amount of ground: SMS, voice calls with full IVR, email with attachments, short links, drip sequences, two-factor codes, a suppression list, an address book, and analytics and pricing for every channel. For an Orchestration as a Service layer that is an unusually complete outreach surface behind one connection, which is exactly why the governance details matter more here than they would on a single-channel gateway.
Two of those details shape every flow built on this connector. The first is that a Go4Clients group is a saved filter, not a membership list. A group is defined by conditions over contact fields, so contacts created later that match those conditions belong to it automatically, and a group with no conditions is refused because it would match nothing or everything. An audience approved on Monday is genuinely a different audience on Thursday, and any flow that treats a group id as a stable set of people is wrong in a way that only shows up at volume. The second is the suppression list, and it deserves its own paragraph.
Go4Clients documents its blacklist status codes in a way that reads backwards: the vendor's own text pairs the code that sounds like adding with the description "Remove the number to blacklist," and the code that sounds like removing with "Add the number to blacklist." Rather than asking a flow author to reason about that at three in the morning, this connector exposes an Effect parameter with two named choices, Add To Blacklist and Remove From Blacklist, required with no default, and maps each to the vendor's code following the vendor's documentation. That mapping has not been confirmed against a live Go4Clients account, so it is worth verifying with one call before a production flow depends on it. Naming that openly is more useful than implying certainty, because the failure mode of getting it backwards is messaging someone who asked you to stop. Everything else on the surface is straightforward: sending has two shapes, a one-shot form that creates and dispatches a campaign in one call, and a build-then-send form where Create SMS Campaign and Add SMS To Campaign let several batches accumulate under one campaign and report together. Voice calls are described by a step list or by the id of an IVR built in the platform, and a call carrying neither is refused before it can be billed for reaching people and playing nothing. Analytics pages are capped at five thousand rows by the vendor. There are no triggers, because none of the four documented callbacks has a subscription endpoint a flow could register against.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A campaign that treats the suppression list as the audience's boundary
A lifecycle team runs a monthly promotion across SMS and email. The agent resolves the audience with List Groups and Get Group, then reads List Blacklist and removes every suppressed destination from the set before anything is priced. Get Balance and Get SMS Pricing turn the remaining count into a number. It builds the send with Create SMS Campaign and Add SMS To Campaign so the whole run reports as one campaign rather than a scatter of one-shot events, and mirrors the email side with Create Email Campaign and Add Email To Campaign. What it does not do is act on the pile of un-suppression requests that customer service has forwarded during the month. Those go into the summary as a separate list, with the original request text attached, for a person to work through.
Short links, drips, and the reporting that ties them together
An onboarding sequence needs to be measurable. The agent calls Create Shortlink for the destination each message points at, groups them with Create Shortlink Campaign and Add Shortlinks To Campaign, and kicks off the sequence with Start Drip Campaign, which either reuses an existing campaign or creates one but never both, so the flow supplies one or the other and never lets the API choose. A week later the reporting is four reads: Get SMS Analytics for delivery, Get Shortlink Analytics for clicks, Get Landing Page Analytics for what happened after the click, and Get Voice Analytics where the sequence included a call. Those land in Google Sheets next to the pricing reads, so cost per outcome is a computed column rather than a quarterly project.
An outbound voice campaign, and the recording nobody meant to make
Go4Clients voice calls are described as a chain of steps: CALL, SAY, SAY_WITH_DTMF, PLAY_AUDIO_URL, PLAY_AUDIO_URL_WITH_DTMF, and HANGUP, routed by keypad digit with a retry path, or by the id of an IVR built in the platform. The agent generates the spoken script with Create Text To Speech Audio, assembles the step chain, and prepares the run with Create Voice Campaign and Add Calls To Campaign. Turning on call recording, though, records the whole call, and whether that is permitted depends on where the recipient is standing rather than where the account is registered. So the agent surfaces that toggle as an explicit question to the campaign owner rather than carrying it forward from a template, naming the destination countries in the run. Afterward, Get Voice Analytics returns the recorded-audio id and Download Audio pulls the file into FlowRunner file storage for whoever needs to review it.
Human-in-Loop Highlight
The gate on Go4Clients is un-suppression, and it is the sharpest one on this connector for three reasons that compound. Update Blacklist Entry with an Effect of Remove From Blacklist, and Delete Blacklist Entry, both put a phone number back within reach of every future campaign on the account. The vendor's own documentation of the underlying codes reads inverted, which makes this the one operation on the platform whose direction is hardest to be confident about. And because Go4Clients groups are saved filters rather than fixed lists, an un-suppressed number does not merely become messageable again, it silently rejoins every group whose conditions it matches, with nobody having re-added it anywhere. A mistake here is not one unwanted message. It is a person who asked to be left alone quietly restored to the audience of every campaign that runs from now on.
So the agent does the collection work and stops before the write. It has already pulled the inbound requests, already matched each number against List Blacklist to confirm it is actually suppressed, already found the original opt-out date. What it posts into Slack is the case rather than a checkbox: "4 numbers requested for removal from the blacklist this week. +57 310 555 0142 opted out 2026-03-11 after a promotional SMS, and wrote in on 2026-08-09 asking to resume order notifications. It matches the conditions on 3 active groups, so removing the suppression puts it back in all 3, including Promo LATAM. Remove the suppression, or handle order notifications on a different channel?" A person answers that in the Flow conversation, and their answer is what runs Update Blacklist Entry.
That is what human-in-the-loop is for. The agent is not asking permission to do something routine, it is holding open the one write whose blast radius extends past this campaign into every future one, on a platform whose own documentation makes the direction of that write ambiguous. Two other operations deserve a person for their own reasons. Delete Group removes a saved filter that other flows may be sending against, and because membership is computed rather than stored there is no list to restore from. Look Up Number is a billed lookup on a read-shaped verb, so a sweep across an unclean contact list spends real money to learn something a person may already know.
Agent Capabilities
43 actionsSMS
3- Send SMS Creates a campaign and dispatches an SMS in one call. The ordinary sending path for transactional messages and one-off sends where nothing needs to accumulate.
- Create SMS Campaign Creates an SMS campaign that batches can be added to before dispatch. Use this form when several batches should report together as one campaign rather than as unrelated events.
- Add SMS To Campaign Adds messages to an existing SMS campaign. The second half of the build-then-send pattern, and what makes a staged run reconcilable afterward.
Voice
3- Create Voice Campaign Creates a voice campaign that calls can be added to. Voice runs are described by a step chain or by the id of an IVR built in the platform, and one or the other is required.
- Add Calls To Campaign Adds calls to an existing voice campaign. Keeps a multi-batch dialing run under one reportable campaign.
- Send Voice Call Creates and dispatches a voice call in one call, driven by a step list or an IVR id. A call carrying neither is refused before it can be billed for reaching people and playing nothing.
- Send Email Creates a campaign and sends an email in one call. The one-shot form for transactional email on the same account and credential as the messaging channels.
- Send Email With Attachment Sends an email carrying a file. Used for invoices, statements, and documents that would otherwise need a separate delivery mechanism.
- Create Email Campaign Creates an email campaign that recipients can be added to before dispatch. The build-then-send form for email.
- Get Email Campaign Retrieves an email campaign's configuration and state. The read a flow uses to confirm what it is about to add recipients to.
- Update Email Campaign Modifies an existing email campaign. Used to correct a subject line or content on a campaign that has been created but not yet dispatched.
- Add Email To Campaign Adds recipients to an existing email campaign. Lets several batches accumulate under one campaign and report together.
Shortlinks
3- Create Shortlink Creates a short link for a destination URL. The unit that makes click-through measurable on a channel where every character is billed.
- Create Shortlink Campaign Creates a campaign that short links can be grouped under. Used when a sequence needs its click data aggregated rather than scattered.
- Add Shortlinks To Campaign Adds short links to an existing shortlink campaign. Keeps a multi-message sequence reporting as one set of links.
Drip Campaigns
1- Start Drip Campaign Starts a drip sequence, either reusing an existing campaign or creating a new one, never both. Supplying an existing campaign id together with a name and sender is refused rather than letting the API decide, which would risk creating a duplicate campaign that also fires.
Verification
2- Create Verification Code Generates and sends a verification code to a destination. This dispatches a real message, so it is a billed send rather than a test operation.
- Validate Verification Code Checks a code the end user entered and returns the outcome. The agent branches on the result rather than handling the code itself.
Analytics
4- Get SMS Analytics Returns delivery and outcome data for SMS traffic. This is the supported substitute for a delivery webhook and what a flow polls after a send.
- Get Voice Analytics Returns outcome data for voice calls, including the recorded-audio id when call recording was enabled. That id is what Download Audio takes.
- Get Landing Page Analytics Returns opens and actions on landing pages. The read that shows what happened after somebody clicked, rather than only that they clicked.
- Get Shortlink Analytics Returns click activity for short links. Paired with the SMS report, this separates a message that arrived from a message that worked.
Account and Pricing
5- Get Balance Returns the account's remaining credit. The cheapest proof the credentials work on a platform that answers a bad credential with a not-found error rather than an authorization error.
- Get SMS Pricing Returns SMS prices for the account. Used to convert a recipient count into a cost before the run is proposed.
- Get Voice Pricing Returns voice call prices for the account. Voice is billed differently enough from SMS that a multichannel campaign needs both figures to be forecast honestly.
- Get Landing Page Pricing Returns landing page prices for the account. Completes the cost picture for a campaign that ends on a hosted page.
- Look Up Number Runs a number lookup. Billed per lookup despite being a read, so a sweep across a large contact list is a deliberate spend rather than a free validation.
Audio
2- Create Text To Speech Audio Generates spoken audio from text for use in a voice campaign. Lets a flow produce a script without a studio step in the middle of it.
- Download Audio Downloads an audio file by id into FlowRunner file storage and returns a URL. The retrieval path for call recordings surfaced by Get Voice Analytics.
Blacklist
4- List Blacklist Returns the suppression list. The precondition read before any send, because a suppressed destination overrides every other audience rule.
- Add To Blacklist Adds a number to the suppression list. This is the direction that should run automatically the moment a reply asks to stop, without waiting for anyone to authorize it.
- Update Blacklist Entry Changes a suppression entry, taking a required Effect of either Add To Blacklist or Remove From Blacklist with no default, which the connector maps to the vendor's code. The removal direction puts a number back in reach of every campaign on the account, which is why it belongs behind a person.
- Delete Blacklist Entry Removes a suppression outright. The most consequential write on this connector, because a saved-filter group will pick the number back up automatically without anyone re-adding it.
Contacts
5- List Contacts Returns contacts with filter and paging support. The address book read behind audience building and record lookups.
- Create Contact Creates a contact, with arbitrary custom fields alongside the mobile number and record id. Custom fields are written first so one named like an identifier cannot redirect a write at another record.
- Update Contact Updates an existing contact. Same identifier protection applies, so a custom field cannot displace the record it is meant to be updating.
- Delete Contact Deletes a contact. Worth remembering that deleting a contact is not the same as suppressing a number, and only the blacklist stops future contact.
- Add Contacts In Bulk Imports many contacts in one call. The onboarding path for a list arriving from a CRM or an event registration.
Groups
5- List Groups Returns the groups defined on the account. Each one is a set of conditions rather than a set of people, which is the single most important thing to hold onto when reasoning about audience size.
- Get Group Returns one group's definition. Reading the conditions is how a flow explains to a person what a group will actually match at send time.
- Create Group Creates a group from conditions over contact fields. A group with no conditions is refused, because it would match either nothing or everyone.
- Update Group Changes a group's conditions. This silently changes the audience of every campaign and drip that targets it, including ones already approved.
- Delete Group Deletes a group. Because membership is computed rather than stored, there is no member list to restore from afterward.
Frequently Asked Questions
What can FlowRunner do with Go4Clients?
FlowRunner agents can run Send SMS, Create SMS Campaign, and Add SMS To Campaign in Go4Clients, plus 40 more actions.
Does connecting Go4Clients to FlowRunner require OAuth?
No. Go4Clients connects to FlowRunner with an API key, no OAuth flow required.
Can Go4Clients trigger a FlowRunner workflow automatically?
Go4Clients doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Go4Clients
$100 in credits. No card required. Connect in minutes.