FlowRunner
PricingContact
Theme
Start Free

Run multichannel campaigns on E-goi, the Portuguese marketing platform, through the official Marketing API V3. Agents manage contacts and lists, send email and SMS, and read campaign results back into the flow.

36 actions API key available
E-goi website ↗ Platform Documentation ↗ Capability data verified 2026-08-02
A campaign report shows a cluster of hard bounces on one recipient domain
Agent pulls the bouncing addresses from Get Email Report and groups them by domain
Agent compares the bouncing addresses against the contacts it holds at that domain
Agent confirms whether the domain has bounced before or whether this is a first occurrence
Agent deactivates the individual bouncing contacts so campaigns stop reaching them
Agent posts the domain, the affected contact count and the account relationship to the marketing channel
Marketing owner decides whether the whole domain goes on the account-wide suppression list

What This Integration Enables

E-goi is the Portuguese multichannel platform, and its API is shaped by a market where consent record-keeping is not an afterthought. That shows up in the operations themselves. Unsubscribe Contacts does not just flip a flag: it stores the unsubscription method, the reason and an observation against every contact in the batch, which is what a complete GDPR audit trail actually looks like. Deactivate Contacts exists as a separate, reversible way to stop mailing someone without touching their consent record at all. Most platforms give you one lever here. E-goi gives you three, and the difference between them is a compliance distinction, not a UI preference.

The rest of the surface is a full campaign lifecycle an agent can drive end to end. It can create a draft email campaign from raw HTML, a saved template or an imported web page, then send or schedule it against the whole list, a set of segments, an explicit contact set, or everyone carrying a tag. It can do the same for SMS, checking the approved cellphone senders and the remaining channel credits first. It can push a batch of contacts into a specific action inside an existing automation flow, which is the API equivalent of a manual trigger and the cleanest way to hand a cohort from a FlowRunner Flow conversation into E-goi's own journey builder. Reports come back into the flow so engagement drives what happens next rather than sitting in a dashboard.

Without FlowRunner

Consent lives in someone's memory An opt-out is recorded as a status change with no reason attached to it
Bounce cleanup is all or nothing A domain with a bad day and a domain that is genuinely dead get the same treatment
Campaign results stay in the platform Open and click data has to be exported before it can drive anything else

With FlowRunner

Every opt-out carries its reason Unsubscriptions record the method, the reason and a free-text note against each contact
Graded responses to bad addresses Deactivation, unsubscription and account-wide suppression are three different decisions
Results feed the next workflow Engagement data returns into the flow and drives scoring, routing and follow-up

Use Case Scenarios

Abandoned cart across two channels with a credit check

A cart is abandoned in Shopify. The agent calls Search Contact to find the person across every list, reads Get Contact Activities to see whether they already received an email in the last 48 hours, and if not, creates and sends a targeted email campaign. If there is still no engagement after a day and the contact has a cellphone on file, the agent checks Get Account Info for remaining SMS credits and Get Cellphone Senders for an approved sender in the recipient's country, then sends the SMS follow-up. If credits are short or no approved sender exists for that country, it stops and says so rather than firing a send that will be rejected at the carrier.

Handing a scored cohort to an E-goi automation

A lead scoring flow in FlowRunner reads product usage and support history from three systems and decides which trial accounts are worth a nurture sequence. Rather than rebuilding that sequence, the agent calls Get Automations and Get Automation Actions to find the right entry point, then Start Automation For Contacts to push the qualified cohort into the flow E-goi's marketing team already built and tested. Scoring lives where the data is. The journey lives where the marketers work.

Segment build from data E-goi does not hold

Renewal dates live in the billing system, not in E-goi. A scheduled agent reads accounts renewing in sixty days from HubSpot, calls Get List Fields to find the right extra field IDs, updates each contact with the renewal window using Update Contact, then calls Create Segment so a saved audience exists inside E-goi for the marketing team to target directly. The segment is defined by rules E-goi can evaluate, but it is populated by facts only the billing system knew.

Human-in-Loop Highlight

The gate is on domain-level suppression, because the suppression list is account-wide and it accepts more than individual addresses. You can suppress a whole email domain in one call, and every contact at that domain is then excluded from every campaign on every list, permanently, with no per-contact consent record explaining why. That is a much larger lever than it looks like sitting in a bounce-cleanup flow. Forty hard bounces at one domain usually means that company's mail server had a bad afternoon, and blanket-suppressing the domain would silently cut off an entire customer account. So the agent handles the individual contacts with Deactivate Contacts, which is reversible, and stops before the bigger write: "Get Email Report shows 43 hard bounces on grupo-exemplo.pt from yesterday's send. I have 118 contacts at that domain, and the account is an active customer. I have deactivated the 43 bouncing addresses. Add grupo-exemplo.pt to the account-wide suppression list, or leave the other 75 contacts mailable?" The agent did the reversible part. The irreversible part waits for a person who knows whether that domain is a dead company or a live customer.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

36 actions

Lists

5
  • Get Lists Retrieves the contact lists in the account with their contact counts and configuration, with pagination, name filtering and sort control. Used to resolve list IDs, which almost every other operation requires.
  • Get List Retrieves a single list including its internal and public names, language settings and per-status contact counts. Used to confirm a list exists and is the right size before importing into it or sending to it.
  • Create List Creates a new contact list. The internal name is what the team sees inside E-goi and the public name is what subscribers see on forms and in campaign footers. Used to provision an audience for a new program without a manual setup step.
  • Update List Updates the internal or public name of an existing list, changing only the values supplied. Used to keep list naming aligned as programs are renamed or restructured.
  • Get List Fields Retrieves every field defined on a list, covering both built-in base fields and custom extra fields. Used to discover the extra field IDs that Create Contact, Update Contact and segment rules all need.

Contacts

9
  • Create Contact Adds a contact to a list with base identity details and any number of custom extra field values, returning the generated contact ID. Used at capture, with phone numbers supplied as country code and number split by a dash.
  • Get Contacts Retrieves contacts from a list with pagination, narrowed by name, email, cellphone, phone, birth date or language, and filterable per channel by subscription state. Used to build working audiences and to export a list for reconciliation.
  • Get Contact Retrieves a single contact by E-goi contact ID with all base fields, channel statuses and extra field values. Used once an ID is known, typically after Search Contact.
  • Update Contact Partially updates a contact, changing only the values supplied. Used for ongoing sync, including subscription status, legal consent basis, per-channel statuses and custom fields. Safe to run repeatedly with a subset of fields.
  • Search Contact Searches every list in the account for a contact matching an email address, cellphone or landline number. Used as the entry point when a flow holds a contact detail rather than an E-goi ID, and returns the list the person belongs to.
  • Get Contact Activities Retrieves a contact's activity timeline covering sends, opens, clicks, bounces, subscriptions, unsubscriptions, tag changes and automation events, filterable by date range and activity type. Used to check recent contact frequency before adding another message.
  • Activate Contacts Reactivates a batch of previously deactivated contacts so they are eligible for campaigns again. Used to reverse a temporary suppression once the reason for it has cleared.
  • Deactivate Contacts Deactivates a batch of contacts so they stop receiving campaigns, without removing them or marking them as unsubscribed. Used as the reversible response to bounces and delivery problems, where a consent record would be the wrong thing to write.
  • Unsubscribe Contacts Unsubscribes a batch of contacts from a list and records the method, reason and a free-text observation against each one. Used to honor an opt-out received outside E-goi while keeping the consent audit trail complete.

Tags

4
  • Get Tags Retrieves the account's tags with their IDs, names and display colors, with pagination and sort control. Used to resolve a tag name to the ID that the attach and detach operations require.
  • Create Tag Creates an account-level tag that can then be applied to contacts in any list, optionally with a display color. Used when a new cohort needs a label that does not exist yet.
  • Attach Tag To Contacts Applies an existing tag to a batch of contacts in a list. Used to mark a cohort so it can serve as a campaign send target or an automation entry condition.
  • Detach Tag From Contacts Removes a tag from a batch of contacts without deleting the tag itself. Used to retire an audience, to reverse a tag applied in error, or as the exit step of an automation that tags on entry.

Segments

2
  • Get Segments Retrieves the segments defined on a list, filterable by whether they are automatic, manually saved or tag derived. Used to resolve segment IDs before targeting a send.
  • Create Segment Creates a saved segment on a list from field rules, with a choice of matching every rule or any rule, and an option to invert the result. Used to define an audience inside E-goi from data the flow just wrote onto the contacts.

Automations

3
  • Get Automations Retrieves the automation flows configured in the account, optionally narrowed to one list, title or activation state. Used to find the automation a cohort should enter.
  • Get Automation Actions Retrieves every action node inside one automation flow, each with the ID that identifies an entry point. Used to pick exactly where in a journey contacts should be injected.
  • Start Automation For Contacts Pushes a batch of contacts into a specific action of an existing automation flow. Used to hand a cohort scored in FlowRunner to a journey the marketing team already built in E-goi.

Campaigns

5
  • Get Campaigns Retrieves campaigns across every channel with filters for channel, delivery status, list, name and creation date range, returning the campaign hash the send and report operations need. Used to locate an existing campaign before sending or reporting on it.
  • Create Email Campaign Creates a draft email campaign on a list, with the body supplied as raw HTML, a saved E-goi template, or a public web page URL that E-goi imports. Requires a verified sender. The campaign stays a draft until it is explicitly sent.
  • Send Email Campaign Sends or schedules an existing draft email campaign to the whole list, to selected segments, to an explicit contact set, or to everyone carrying a tag. Supplying a schedule date queues it for later instead of sending immediately.
  • Create SMS Campaign Creates a draft SMS campaign on a list with the message body, an optional approved sender, and a cap on concatenated message parts to control cost. Used when the follow-up needs a channel with a higher chance of being read.
  • Send SMS Campaign Sends or schedules an existing draft SMS campaign to the whole list, to segments, to explicit contacts, or to everyone carrying a tag. Used as the second channel in an escalating sequence, after the credit and sender checks have passed.

Reports

2
  • Get Email Report Retrieves the delivery and engagement report for a sent email campaign, including sends, opens, clicks, bounces and unsubscriptions, with optional breakdowns by date, weekday, hour, location, recipient domain, clicked URL and email client. Used to drive follow-up logic and to spot domain-level delivery problems.
  • Get SMS Report Retrieves the delivery report for a sent SMS campaign including messages sent, delivered, failed and the resulting cost. Used to reconcile SMS spend and to catch carrier delivery failures after a send.

Senders

2
  • Get Email Senders Retrieves the registered email sender addresses with their verification state. Used as a preflight check, since only senders in the Active state can send campaigns.
  • Get Cellphone Senders Retrieves the alphanumeric or numeric cellphone sender IDs approved on the account. Used before assigning a sender to an SMS campaign, because many countries restrict which sender IDs are permitted.

Suppression List

2
  • Get Suppression List Retrieves the account-wide suppression list, filterable by entry type, how the entry was added, value and creation date range. Used to check whether an address is already blocked before a flow tries to mail it.
  • Add To Suppression List Adds values to the account-wide suppression list so they are excluded from every future campaign. Accepts individual addresses and numbers, and also whole email domains and email local parts. The domain form has a very large blast radius, which is why it belongs behind a review step.

Account

2
  • Get Account Info Retrieves the authenticated account profile including client identifier, company details, plan information and remaining channel credits. Used to verify credentials and to check credit balances before launching an SMS or voice campaign.
  • Get Queued Operations Retrieves the asynchronous operations E-goi has queued, such as bulk imports, activations, unsubscriptions and tag changes. Used to confirm a batch action submitted earlier in the flow actually finished, and to read any errors it produced.

Frequently Asked Questions

What can FlowRunner do with E-goi?

FlowRunner agents can run Get Lists, Get List, and Create List in E-goi, plus 33 more actions.

Does connecting E-goi to FlowRunner require OAuth?

No. E-goi connects to FlowRunner with an API key, no OAuth flow required.

Can E-goi trigger a FlowRunner workflow automatically?

E-goi doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with E-goi

$100 in credits. No card required. Connect in minutes.