Sounds like a good idea, André!

Really nice to see the supported integrations growing!

Thanks & Regards,
Amogh Desai


On Fri, Mar 6, 2026 at 3:17 PM Jarek Potiuk <[email protected]> wrote:

> Yep. And yes. It's a nice one to contribute!
>
> On Fri, Mar 6, 2026 at 9:37 AM Zhe-You(Jason) Liu <[email protected]>
> wrote:
>
> > Hi A. Ahlert,
> >
> > Thank you for your interest in adding an official Stripe provider for
> > Airflow!
> > We need to follow the adoption path described in AIP-95 [1], similar to
> the
> > recent Informatica provider [2].
> >
> > It would be better to start by opening a draft PR and then initiating a
> > voting thread on the dev mailing list.
> >
> > Thanks!
> >
> > [1]
> >
> >
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-95+Provider+lifecycle+update+proposal
> > [2] https://lists.apache.org/thread/wsfgh23jm6hkrly4lx1m21ftllqshpgo
> >
> >
> > Best regards,
> > Jason
> >
> > On Fri, Mar 6, 2026 at 5:22 AM André Ahlert <[email protected]> wrote:
> >
> > > Hi all,
> > >
> > > Is anyone interested in having an official Stripe provider in Airflow,
> > and
> > > willing to help review or support it?
> > >
> > > At AEX we run production pipelines that pull Stripe data for revenue
> and
> > > finance analytics. Today there’s no official Stripe provider, and the
> > > community plugin https://github.com/airflow-plugins/stripe_plugin
> > > <
> https://github.com/airflow-plugins/stripe_plugin?utm_source=chatgpt.com
> > >
> > > hasn’t been updated since 2018, so we’ve been maintaining a private
> fork
> > to
> > > keep things working with current Airflow. I’d like to upstream a proper
> > > provider-standard implementation.
> > >
> > > What I’m proposing (starting small):
> > >
> > >    -
> > >
> > >    apache-airflow-providers-stripe
> > >    -
> > >
> > >    StripeHook using an Airflow Connection (API key as the secret,
> extras
> > >    for non-secret settings)
> > >    -
> > >
> > >    Pagination + retries/backoff for rate limits
> > >    -
> > >
> > >    Minimal operator surface area at first: hook-only, or one generic
> > >    extraction operator
> > >    -
> > >
> > >    No Stripe-to-S3 coupling; examples can show how to land data using
> > >    existing providers
> > >
> > > Implementation would use the official Stripe Python SDK and be tested
> > > without calling the real API (stripe-mock + unit tests).
> > >
> > > If there’s enough interest, I’ll open a draft PR and follow the
> provider
> > > onboarding process, including lining up additional stewards and a
> > committer
> > > sponsor.
> > >
> > > Questions:
> > >
> > >    -
> > >
> > >    Are you interested in an official Stripe provider?
> > >    -
> > >
> > >    Would you prefer v1 to be hook-only, or hook + one generic
> extraction
> > >    operator?
> > >    -
> > >
> > >    If we include an operator, which objects should come first
> (customers,
> > >    subscriptions, invoices, events)?
> > >
> > > Thanks,
> > > A. Ahlert
> > >
> >
>

Reply via email to