DEV

Stripe

Stripe Connection

Put Stripe to Work with @Human Automations and @Human Agents

The Stripe Connection documents all Triggers, Actions and Query Operations available for creating automations via the Stripe API.

What can you do with the [Name] Connection?

  • Connect to the Stripe API in a few clicks

  • Use the related Stripe Operations (see below) in @Human Automations or @Human Agents

Trigger Operations

Customer Created

Triggers on: customers/customer.created

Triggered when a new customer is created in Stripe.

Customer Updated

Triggers on: customers/customer.updated

Triggered when an existing customer is updated in Stripe.

Charge Succeeded

Triggers on: charges/charge.succeeded

Triggered when a charge is successfully completed in Stripe.

Subscription Created

Triggers on: subscriptions/customer.subscription.created

Triggered when a new customer subscription is created in Stripe.

Payment Intent Succeeded

Triggers on: payment_intents/payment_intent.succeeded

Triggered when a payment intent has successfully completed in Stripe.

Invoice Paid

Triggers on: invoices/invoice.paid

Triggered when an invoice is fully paid in Stripe.

Checkout Session Completed

Triggers on: checkout_sessions/checkout.session.completed

Triggered when a Checkout Session has been successfully completed in Stripe.

Action Operations

Action: Cancel Subscription

Action: Create Checkout Session

Action: Create an Invoice

Action: Create a Payment Link

Action: Create a Product

Action: Confirm a Payment Intent

Action: Create a Customer

Action: Create a Payment Intent

Action: Create a Price

Action: Create a Subscription

Action: Update a Customer

Query Operations

Example link

Example link

Obtaining Access Credentials

To obtain a Stripe system-to-system Personal Access Token (PAT), follow these steps:

Required Values (Request from User)

  1. Stripe Account Email (Admin/Owner access required)

  2. Stripe Account Password (if not already logged in)

Steps to Generate the Token

  1. Log in to the Stripe Dashboard: → https://dashboard.stripe.com (Use the provided Stripe Account Email and Password.)

  2. Navigate to Developers → API Keys:

    • Click "Developers" in the left sidebar.

    • Select "API Keys" under the API section.

  3. Create a Restricted Key (Recommended for System-to-System Access):

    • Under "Standard keys", click "Create restricted key".

    • Provide a name (e.g., System-Integration-PAT).

    • Under "Restrict by resource type", select the required permissions (e.g., Read/Write for Charges, Customers, etc.).

    • Click "Create key".

  4. Copy the Token:

    • The Secret Key (e.g., sk_live_...) will appear once. Copy it immediately.

    • (This is your PAT—treat it as a secret.)

  5. Secure the Token:

    • Store it securely (e.g., secrets manager, encrypted config).

    • Never commit it to version control.

Token Format: sk_live_<random_string> (for live mode) or sk_test_<random_string> (for test mode).

Configuring Webhooks

  1. Log in to the Stripe Dashboard: → https://dashboard.stripe.com

  2. Navigate to Developers → Webhooks:

    • Click "Developers" in the top navigation or left sidebar.

    • Select "Webhooks" (you may need to open the Webhooks tab within the Workbench section if available).

  3. Add a Webhook Endpoint:

    • Click "Add endpoint" (or "Create an event destination").

    • In the "Endpoint URL" field, provide your publicly accessible HTTPS URL.

    • Click "Select events" and choose the required event types (e.g., checkout.session.completed).

    • Click "Add endpoint".

  4. Retrieve and Secure the Signing Secret:

    • On the endpoint's details page, click "Reveal" in the Signing secret section.

    • Copy the secret (starts with whsec_...) and store it securely in your application's environment.

Code (Apache v2.0): Service Connectivity and Metadata

Code (Apache v2.0): List of External Resources and Internal Mapping

Last updated