Outside systems plug into Workspace Studio, a dead domain needs purging, and pre-warmed inboxes go on sale (2026)

Coverage window: September 16, 2026 at 10:16 through September 18, 2026 at 10:15 (UTC+02:00). The three items below are ranked by how directly they change an email team's automation plumbing, the hygiene of its lists, and the way sending reputation gets acquired.

1. Workspace Studio now takes custom starters, custom steps, third-party integrations and webhooks

What changed

Google turned on four new capabilities in Workspace Studio, the automation product inside Workspace, on September 17, 2026. Custom starters let a team build a real-time trigger from an event in another application and use it to run a flow. Custom steps let a flow run logic written in-house, using Apps Script. Webhooks let a flow send an HTTP request to an external endpoint and start work there. Third-party integrations, still in beta, connect Asana, Confluence, HubSpot, Jira, Mailchimp, QuickBooks, Salesforce and Slack so data passes between Workspace and those services. 1

All four arrive switched off. An administrator enables them in the Admin console under Apps, Google Workspace, Workspace Studio, where custom steps, integrations and webhooks each have their own setting. Approval requirements are configured in the same place, and webhook steps follow the approval settings for sensitive steps. 1

The administrator controls and the end-user features roll out on separate schedules. Admin console settings reached full rollout from September 17, 2026. End-user features begin on September 21 for Rapid Release domains and September 30 for Scheduled Release domains. Availability covers Business Starter, Standard and Plus, Enterprise Standard and Plus, and Education Fundamentals, Standard and Plus, while the webhook URL allowlist that limits which external endpoints a flow may call is restricted to the higher Business, Enterprise and Education editions. 1

Why it matters

Most email teams already run marketing automation in one system and company workflow in another, and the joint between them has been manual work: an export, a bridging tool that passes a payload, or a developer writing a one-off integration. Third-party steps and webhooks move that joint inside Workspace, and a custom starter lets the trigger originate in whichever system already knows that a customer changed state. For a team sending through Mailchimp, or holding contact data in HubSpot or Salesforce, the distance between a business event and a send gets shorter.

The reason to look before enabling anything is that these features put the ability to send mail and write to contact records inside a flow that a team outside marketing can build and edit. Whether a person has to approve an external send becomes an admin setting in the Workspace console, so a control that used to sit in the sending platform's permission model lives somewhere else from now on.

Checks before acting

Decide across marketing, IT and compliance whether these features should be enabled in your organisation at all, since they arrive off by default and the decision is the administrator's.
Set the human-approval requirement for integrations and custom steps, and check how webhook steps inherit the approval rule for sensitive steps.
List the Gmail and Mailchimp actions a flow can now reach, and agree which of them may run without a person confirming.
Confirm whether your edition includes the webhook URL allowlist, and if it does, agree which external endpoints are permitted before anyone builds against them.
Test on your own release track, since Rapid Release domains see the end-user features on September 21 and Scheduled Release domains wait until September 30.

2. A retired regional email domain that has to come off your lists

What changed

Spam Resource flagged a dead email domain on September 16, 2026. Ting Internet, which Tucows owns, bought the regional communications provider Cedar Networks, also known as Zippytech, in November 2019 and has since retired the legacy email hosting that came with it. Every mydurango.net address stopped working on March 12, 2026, and users lost account access the day before. Ting's own support page states that the service was permanently discontinued, with no way to restore accounts or recover mail. 2 3

The advice that comes with it is to remove and suppress any surviving @mydurango.net addresses, because a retired regional mailbox provider is the kind of domain that later gets revived as a spamtrap feed. Subscribers on the domain came from Colorado and New Mexico. 2

Why it matters

An address on a domain with no mail service bounces hard today, which is the manageable half of the problem. The other half arrives if someone registers the domain later and runs it as a trap: mail sent to those addresses then registers as a complaint-class signal, and mailbox providers read it as evidence that the list is not maintained. The penalty lands on the sending domain, whichever list the address came from, and it survives the campaign that triggered it.

Regional and legacy provider domains are where this accumulates quietly. They arrive in a list through an old signup form, an event spreadsheet or a CRM import, they sit there for years, and no bounce ever removes them because nobody sends to that segment any more.

Checks before acting

Search every sending audience, CRM and imported spreadsheet for @mydurango.net addresses, not only the main marketing list.
Suppress the domain rather than deleting individual records, so a later import cannot bring the addresses back.
Run the same check against other retired regional provider domains you may hold, since the pattern repeats across small internet and cable providers.
Block the domain at import as well as at send, so it cannot re-enter through a form or a file.
Query your list for addresses whose domains have no MX record; the same class of problem shows up in that result within minutes.

3. Pre-warmed mailboxes are now a product you can rent

What changed

EmailPal launched on September 17, 2026, selling infrastructure for cold outbound email: domain registration, mailbox provisioning, authentication, inbox warming, deliverability monitoring and list verification in one system, reachable through a dashboard, a REST API and a server for AI agents. The centrepiece is pre-warmed inventory, which the company describes as addresses on domains it registers, parks and warms months before selling them. Pre-warmed addresses rent at $3 per address per month on a 90-day minimum term, with warming continuing for the life of the lease, and mailbox plans start at $69 per month for 50 mailboxes, $189 for 200 and $499 for 600. 4

The company says every sending address is scored hourly against Gmail, Microsoft and Yahoo separately, and that an address steps down through watch, throttled and quarantine states as its signals degrade and recovers automatically once it sends cleanly again. Authentication is configured for the customer, with SPF set to hard fail, DKIM using both RSA-2048 and Ed25519 keys, DMARC at p=reject, and reply MX records in place. Alongside the API the company ships 29 tools for AI agents, with a read-only mode that withholds purchasing, releasing and sending. 4

These are the vendor's figures and claims from its launch announcement. EmailPal publishes no measurement behind the hourly scores, and describes its mailboxes at roughly $1 each against about $16 per seat on the infrastructure most outbound teams use instead. 4

Why it matters

Renting warm reputation turns a deliverability question into a purchasing decision, and that is where the details decide the outcome. Mailgun's guidance on warm-up tools sets out the objection plainly: reputation is a running evaluation of who is sending, what they send, to whom, and how those recipients respond, recalculated continuously rather than awarded once. A new sender taking over previously warmed infrastructure gets recalibrated against the new traffic, so the history the buyer paid for stops describing what is now being sent. 5

The product also makes a specific arrangement worth naming before anyone signs: the sending domain, the DNS records and the reputation history belong to the vendor. That is a different proposition from running outbound on your own domain and it changes what happens at renewal, at cancellation, and the first time a recipient complains.

Checks before acting

Establish who owns the sending domain and who controls its DNS, SPF, DKIM and DMARC records when the addresses are rented rather than owned.
Test placement from the rented infrastructure with your own content, cadence and audience, instead of relying on a placement rate that ships with the inventory.
Confirm the addresses have reply MX records and that replies reach a mailbox your team reads, since a rented domain that receives nothing is a one-way channel.
Keep cold outbound on separate domains and separate sub-accounts from your customer marketing sends, so a suspension on one side cannot reach the other.
Check what survives the end of the lease: which addresses you keep, which warm-up history stays with the vendor, and how a new domain starts from zero afterwards.

Next audit

Find every address in your sending audiences whose domain no longer resolves, beginning with @mydurango.net, and suppress the domain rather than the record. Then ask who in your organisation can now build an automation that sends mail, and whether a person has to approve it. If anyone is pricing warmed inboxes, establish whose domain the reputation is attached to before the invoice is signed.