RFC: Integration adapters for afterBuild

[preston176]

Problem

Teams are writing one-off scripts to connect Maizzle with testing platforms (Litmus, Email on Acid) and email services (Postmark, Resend, SendGrid). See #420 for an example.

Everyone reimplements the same patterns—API calls, error handling, rate limiting, file filtering. No code sharing, inconsistent approaches, knowledge stuck in private repos.

Proposal

Official adapter package for common afterBuild integrations:

import { createAdapter } from '@maizzle/integrations'

export default {
  afterBuild: createAdapter({
    providers: [
      { name: 'litmus', apiKey: process.env.LITMUS_API_KEY },
      { name: 'postmark', serverToken: process.env.POSTMARK_TOKEN },
      { name: 'webhook', url: 'https://custom-tool.com/api' }
    ],
    filter: (file) => file.endsWith('.html'),
    onError: 'warn',
    parallel: true,
    rateLimit: { requests: 10, per: 'second' }
  })
}

Start with: Litmus, Email on Acid, Postmark, generic webhook. Add Resend/SendGrid/others later.

Benefits: Drop-in solution with error handling and rate limiting. Standardized CI/CD pattern. Version-controlled config.

My offer

I run an email testing platform and will:

• Build and maintain this package
• Include my platform as one adapter but keep it generic (Litmus, Postmark, etc. are first-class)
• Write docs
• Coordinate with other vendors if interested

Follows #91 philosophy: separate package, zero core changes, opt-in, community can contribute adapters.

Questions

1. Worth solving?
2. @maizzle/* namespace or community package?
3. Which integrations first?

Can submit a PR with core architecture if this sounds good.

References:

• #91: afterBuild event
• #420: Postmark CI/CD integration

[cossssmin]

Hi Preston, sorry for the delay in replying. I think this can start as a community package which users would run in the afterBuild event, see how it goes and we take it from there 👍