Stripe, Monday and Slack: New-Subscription Onboarding Template

When a new Stripe subscription starts, this Spojit template opens a Monday onboarding item and pings your success team in Slack with the plan and customer name.

What It Builds

A Webhook trigger receives Stripe's new-subscription event, verified by a Stripe signing connection. From the event payload, a Connector node on Monday runs create-item to add an onboarding card to your customer-success board, and a second Connector node on Slack runs send-message to post the plan and customer name into your success channel. The result is a hands-free onboarding handoff the moment money starts flowing.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow with a Webhook trigger that receives a new Stripe subscription event. Create a Monday item on the "Customer Onboarding" board titled with the customer name, then send a Slack message to the #customer-success channel saying a new subscriber just signed up, including the plan name, the customer name, and the customer email.

Connectors Used

  • Webhook trigger - receives Stripe's subscription event as JSON, verified with a Stripe signing connection.
  • Stripe - the source system; you can add a Connector node running get-customer if the webhook only carries an ID and you need the full name and email.
  • Monday - create-item opens the onboarding card on your chosen board.
  • Slack - send-message notifies your success channel.

Customize It

Change the Monday board name, the Slack channel (for example #onboarding), and the message wording in the prompt before you run it. If you want different cards per tier, ask Miraxa to add a Condition node that routes premium plans to a separate board or channel. You can also point the trigger at Stripe's customer.subscription.updated event instead, to react to upgrades rather than new sign-ups.

Tips

  • Set the Webhook trigger's signing connection scheme to Custom with Stripe's signing secret so only genuine Stripe events run the workflow.
  • Use Direct mode on the Monday and Slack nodes: each call is a single predictable action, so you avoid AI credits and get deterministic output.
  • Reference fields with handlebars such as {{ input.data.object.customer_email }} and {{ input.data.object.plan.nickname }} so the message stays accurate as payloads vary.

Common Pitfalls

  • Stripe webhooks sometimes carry only IDs. If the customer name is missing, add a Stripe get-customer step before the Monday node to resolve the full record.
  • The Slack connection must be invited to the target channel first, or send-message cannot post there.
  • Stripe may retry the same event. Turn on the Webhook trigger's dedup option using the event-id header so a single subscription does not create duplicate Monday cards.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.