Bring Stripe customer context into AccuLynx follow-up
Get the billing context you need while handling a job, without searching Stripe manually.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve customer
Retrieves detailed information for an existing stripe customer using their unique customer id.
Why this helps
Looking up billing records interrupts project follow-up and makes it easier to miss useful context.
- Retrieve a Stripe customer record from a job follow-up request.
- Reduce app switching during customer conversations.
- Make billing details available for the next decision.
Setup
Build it in a few focused steps.
- 1Connect AccuLynx and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to retrieve the Stripe customer identified by the details included with the AccuLynx job request and summarize relevant returned information.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real job and confirm the report contains the expected customer.
Questions about this workflow
What does Notis need to find the customer?
A Stripe customer ID is the clearest identifier. If using other identifying details, provide them in the request.
Will this change the Stripe customer?
No. This workflow retrieves customer information for follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Acculynx to Stripe. A trigger fires from one place; an action lands in another.
Acculynx 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.
Acculynx 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.