shadcn.io is not affiliated with official shadcn/ui
Live Record Setup Mailchimp Integration Block for React
An integration setup for a signup-form tool connecting to Mailchimp: three steps (audience, consent, tags) beside the JSON request one signup would send, which changes as you choose.
Installation
Overview
An integration setup section for React with Base UI, written for Wrenlist, a fictional signup-form and embed tool, and its Mailchimp connection. A compact header names the product and the service, with the mark pair (Wrenlist's own tile and Mailchimp's neutral lettermark tile) at its end. Under a band rule, the start column holds the catalog's Steps: pick the audience a signup joins (a Select with example contact counts), choose how people consent (a switch for double opt-in, which adds them as pending until they click Mailchimp's confirmation link, or as subscribed at once) and add default tags (a tags input, up to five). Each Continue waits for what its step needs and a line says what is missing; the last step's Shine Button, Finish setup, ends on Connected in this demo with a quiet Disconnect. Behind a split divider, a window shows the JSON request one example signup would send, the audience in its path, the status and the tags: it rewrites itself as you choose, and its Copy button copies it. Every step sits in one grid cell with an unseen copy of them all, so the block keeps the tallest step's height. Nothing is sent to Mailchimp. Mailchimp is named in text only, with no logo, colour or wordmark; the audiences, counts and the sample address are example data.
FAQ
Does Finish setup connect to Mailchimp?
No. Finish setup only moves the block to its Connected in this demo state, and the status line says that nothing was sent to Mailchimp. The request in the window is what your server would send for each signup, so wire Finish setup to your own OAuth or key step, and send the request from your signup handler. The sample address is ines.rowe@example.com, never a real one.
Is the request real Mailchimp?
Yes, in shape. It is a POST to the audience's members path, with email_address, status, merge_fields and tags, which are fields of Mailchimp's Marketing API for adding a member. The path still says lists, because the API kept that name when Mailchimp began calling them audiences, and the audience id in it is a made-up example id. Edit recordLines at the top of the file to add or drop fields.
What does the consent switch change?
With double opt-in on, the request carries "status": "pending": Mailchimp emails a confirmation link and the person becomes subscribed when they click it. With it off, the status is subscribed and they count at once, which is only right when your form already records their consent. The line under the switch and the request both follow it.
How do the tags work?
The tags input takes a tag when you press Enter or comma, or when you leave the field, skips duplicates whatever their case, and stops at five in this demo. Each one appears as a string in the request's tags list. The remove button on a tag, or Backspace in an empty field, takes it out.
How do the steps behave for keyboard and screen reader users?
The Steps list shows a number and a title for each step; the titles hide on a phone and stay readable by screen readers. A step you haven't reached can't be opened. When you press Continue or Back, the new step's heading takes focus and a polite line says the step you are on. The first step's Continue waits until an audience is chosen and says so in words.
Can I show Mailchimp's logo?
The block names Mailchimp in text and ships no logo, colour or wordmark. Its tile is a neutral lettermark, Mc in a muted square, in an icon slot that a code comment marks: drop in the official mark only if you have the rights to use it under the owner's brand guidelines, and never redraw it.
How does it fit on a phone, in right-to-left layouts and with reduced motion?
On a phone the steps come first and the window falls below them, with a rule between. In a right-to-left layout the columns flip, while the request keeps its left-to-right direction in a scrollable, focusable region. The entrance is a CSS transition that is dropped under reduced motion.
Related
- Pro
Day-Grouped Timeline Mailchimp Integration
Grouped and triagedAn integration list for a signup-form tool writing to Mailchimp: subscriber events under day headings, a segmented filter that dims the rest, and Retry sync on the one write that failed.
- Pro
List Growth Bridge Mailchimp Integration
Bars and columnsAn integration stats section for a signup-form tool writing to Mailchimp: a bridge of floating bars from the opening audience through signups, resubscribes, unsubscribes and cleaned addresses to the closing figure.
- Pro
Mailchimp Detail Integration
Scopes and stepsAn integration detail section for a signup-form tool connecting to Mailchimp: a three-step timeline, the Connect Mailchimp Shine Button, and a framed panel of real tabs (Reads, Writes, Never) listing the audience fields touched.
- Pro
Mailchimp Grid Integration
Cards and previewsAn integration grid section for a signup-form tool writing to Mailchimp: six welcome-journey cards apart on overshoot corners, each with a Switch and a drawn three-node flow (trigger, wait, email), and a derived tally of journeys on.
- Pro
Frame Thumbnails Setup Integration
Guided stepsAn integration setup section for a design-docs tool connecting to Figma, in one framed window: paste a personal access token, tick greyscale wireframe thumbnails of the frames to link, name the link and watch its address follow, then finish with an honest result.
- Pro
Menu Path Setup Notion Integration
Choose and verifyAn integration setup for a meeting-notes tool connecting to Notion: three cells with a drawing of each screen (the secret, the page menu, the connections list), a secret field, a check that finds two pages and locks one, and a Finish setup.