---
title: "Workflows: Automatically customize an object with metadata"
description: "Stripe Workflows can customize Stripe objects with metadata, adding contextual key-value information without changing the core data model or storing it separately. The example targets customers associated with successful Payment Intents that include a tip, so a customer can be labeled for business use, such as reconciliation, reporting, or internal integrations. To build it, the workflow retrieves the customer from the Payment Intent, emails a team member, checks whether the successful Payment Intent contains a non-empty tip amount, and updates that customer with the metadata key Tier and value VIP. Workflows runs a trigger and sequential actions or conditions in a visual Stripe Dashboard builder, while metadata can carry information to later workflow steps and support automation, analytics, and debugging."
---

# Workflows: Automatically customize an object with metadata

[Stripe](https://yomu.fyi/company/stripe) · Ashley Ansari · Jul 22, 2025

**Type:** Tutorial

## Summary

Stripe Workflows can customize Stripe objects with metadata, adding contextual key-value information without changing the core data model or storing it separately. The example targets customers associated with successful Payment Intents that include a tip, so a customer can be labeled for business use, such as reconciliation, reporting, or internal integrations. To build it, the workflow retrieves the customer from the Payment Intent, emails a team member, checks whether the successful Payment Intent contains a non-empty tip amount, and updates that customer with the metadata key Tier and value VIP. Workflows runs a trigger and sequential actions or conditions in a visual Stripe Dashboard builder, while metadata can carry information to later workflow steps and support automation, analytics, and debugging.

## Context

Developers may need to attach internal identifiers, campaign names, order numbers, or other contextual information to Stripe objects for reconciliation, reporting, integrations, analytics, debugging, and automated backend actions. The example focuses on identifying customers who left a tip.

## Approach / What changed

Create a Stripe Workflow triggered by Payment intent succeeded. Retrieve the customer using the Payment Intent's Customer ID, email a team member, test whether Amount details > Tip > Amount is not empty, and update the customer with metadata using the key Tier and value VIP.

## Takeaways

- Stripe metadata stores additional information as key-value pairs on certain objects, including Customer and PaymentIntent, without modifying the core data model.
- The workflow condition checks that the successful Payment Intent has a non-empty tip amount before updating the related customer.
- A workflow consists of a trigger followed by sequential actions and conditions, and metadata can pass information to subsequent workflow steps.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Developer Experience](https://yomu.fyi/topic/developer-experience)

- Source: [Stripe](https://stripe.dev/blog/workflows-customize-objects-metadata)
- Source URL: https://stripe.dev/blog/workflows-customize-objects-metadata
- Ingested by Yomu: 2026-08-28T08:59:20.285Z

[Read original post](https://stripe.dev/blog/workflows-customize-objects-metadata)