Add customer context to campaign research
Use your keyword plan and customer records together when deciding which audience questions a campaign should address.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List customers
Retrieves a list of stripe customers, with options to filter by email, creation date, or test clock, and support for pagination.
Why this helps
Campaign planning can rely on search trends alone and miss context already available in customer records.
- Bring Ahrefs keyword findings and Stripe customer records into one planning report.
- Give campaign discussions more business context.
- Use an HTTP request to start a review when your planning process is ready.
Setup
Build it in a few focused steps.
- 1Connect Ahrefs and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to analyze the supplied campaign topic in Ahrefs, retrieve relevant Stripe customer records, and summarize planning context without changing customer data.
- 4Pick a webhook as the trigger and choose where run reports go.
- 5Test with one real example by sending an HTTP request for a campaign topic.
Questions about this workflow
What starts this workflow?
A Notis webhook starts it when it receives an HTTP request.
Does this target or message customers?
No. It retrieves customer records for planning context and does not send communications.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ahrefs to Stripe. A trigger fires from one place; an action lands in another.
Ahrefs triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Ahrefs and Stripe, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Stripe.