@drawbridge/drawbridge-utils 0.0.169 → 0.0.170

package/dist/connections/index.cjs

@@ -3337,6 +3337,7 @@ var klaviyo_default2 = {
         if (!email) return { message: "That lead has no email address to sync.", skipped: true };
         const person = (context == null ? void 0 : context.contact) || null;
         const totals = (person == null ? void 0 : person.totals) || {};
+        const count = (value) => typeof value === "number" ? value : (value == null ? void 0 : value.total) || 0;
         const profile = await api2("/profile-import", {
           fetcher,
           method: "POST",
@@ -3350,13 +3351,13 @@ var klaviyo_default2 = {
                     drawbridge_campaigns: (person.campaigns || []).length,
                     drawbridge_draws: totals.draws || 0,
                     drawbridge_entries: totals.entries || 0,
-                    drawbridge_orders: totals.orders || 0,
+                    drawbridge_orders: count(totals.orders),
                     // Campaign-attributed, NOT lifetime. A merchant running
                     // Shopify already has lifetime revenue in Klaviyo through
                     // Klaviyo's own integration; what only we can say is how
                     // much a campaign drove. Named so the two cannot be
                     // mistaken for one another in a segment builder.
-                    drawbridge_revenue: totals.gross || 0
+                    drawbridge_revenue: count(totals.gross)
                   },
                   // THE DRAWBRIDGE SEGMENTS THEY ARE IN, as a list property the
                   // merchant builds Klaviyo segments on top of. Klaviyo owns no
@@ -3861,7 +3862,8 @@ var api3 = async (path, { dc, fetcher = fetch, method = "GET", payload, token })
   return response.status === 204 ? null : response.json();
 };
 var subscriberHash = (email) => (0, import_node_crypto5.createHash)("md5").update(String(email).trim().toLowerCase()).digest("hex");
-var tagName = (title) => "Drawbridge: " + title;
+var TAG_NAME_LIMIT = 100;
+var tagName = (title) => ("Drawbridge: " + title).slice(0, TAG_NAME_LIMIT);
 var mailchimp_default2 = {
   // OAUTH 2, authorization code. Every url below is quoted from
   // mailchimp.com/developer/marketing/guides/access-user-data-oauth-2/ rather
@@ -4086,10 +4088,12 @@ var mailchimp_default2 = {
       // on attaching people to it by name. Both address the same object. The
       // segment schema says it outright: "The type of segment. Static segments
       // are now known as tags"
-      // (api.mailchimp.com/schema/3.0/Swagger.json, fetched 2026-09-11).
+      // (api.mailchimp.com/schema/3.0/Definitions/Lists/Segments/Response.json,
+      // fetched 2026-09-12 — the root Swagger.json carries no prose, only $refs
+      // into fragment files like this one).
       //
-      // IDEMPOTENT ON EVERY PATH: called on create, on rename, on the boot
-      // sweep and on backfill, it converges. That is what lets one hook serve
+      // IDEMPOTENT ON EVERY PATH: called on create, on rename, on a connection
+      // finishing its configuration, and on the backfill migration, it converges. That is what lets one hook serve
       // all four without a create-vs-update branch anywhere else.
       register: async ({ connection: connection2, context, manifest, settings, token, workflow }, { fetcher, read } = {}) => {
         var _a;

package/dist/connections/index.d.cts

@@ -3867,6 +3867,13 @@ var klaviyo = {
 				// fetched 2026-09-09).
 				//
 				// IT MERGES, and that is why the blocks below are conditional rather
+				// GROUPED OR FLAT, read as one number. contact.totals.orders and .gross
+				// are { total, conversions, redemptions } now, but a contact the
+				// backfill has not reached still holds the old flat number — and a
+				// naked `totals.orders || 0` would hand Klaviyo the whole object as a
+				// profile property. Klaviyo gets the total either way.
+				const count = ( value ) => typeof value === 'number' ? value : ( value?.total || 0 );
+
 				// than defaulted. "Not including a field in your request will leave it
 				// unchanged" — so omitting the totals on a lead.insert preserves
 				// whatever the last segment run published, where sending zeros would
@@ -3884,13 +3891,13 @@ var klaviyo = {
 										drawbridge_campaigns : ( person.campaigns || [] ).length,
 										drawbridge_draws : totals.draws || 0,
 										drawbridge_entries : totals.entries || 0,
-										drawbridge_orders : totals.orders || 0,
+										drawbridge_orders : count( totals.orders ),
 										// Campaign-attributed, NOT lifetime. A merchant running
 										// Shopify already has lifetime revenue in Klaviyo through
 										// Klaviyo's own integration; what only we can say is how
 										// much a campaign drove. Named so the two cannot be
 										// mistaken for one another in a segment builder.
-										drawbridge_revenue : totals.gross || 0
+										drawbridge_revenue : count( totals.gross )
 									}),
 									// THE DRAWBRIDGE SEGMENTS THEY ARE IN, as a list property the
 									// merchant builds Klaviyo segments on top of. Klaviyo owns no
@@ -4616,7 +4623,24 @@ const subscriberHash = ( email ) => createHash( 'md5' )
 // THE TAG'S NAME, and the one place it is spelled. The member write and the
 // register hook must agree character for character — they address the same
 // object, one by name and one by id — so a prefix change is one edit here.
-const tagName = ( title ) => 'Drawbridge: ' + title;
+//
+// TRUNCATED TO 100, because that is Mailchimp's documented ceiling for a tag
+// name ("Tag names can be a maximum of 100 characters",
+// mailchimp.com/help/create-add-remove-tags, fetched 2026-09-12) and a segment
+// title can be 100 on its own — so the prefix pushes any title over 88 past it.
+// The limit is in their help centre and NOT in the API schema, which constrains
+// `name` to a bare string, so what the API does with an over-long name is
+// unspecified: it may reject the whole write or truncate server-side, and a
+// server-side truncation is the worse outcome because register would then look
+// for a name Mailchimp had silently changed.
+//
+// ponytail: two segments whose first 88 characters match would share one tag.
+// The upgrade is to append a short hash of the segment id, which costs the name
+// its readability in the merchant's own audience — not worth it until somebody
+// actually collides.
+const TAG_NAME_LIMIT = 100;
+
+const tagName = ( title ) => ( 'Drawbridge: ' + title ).slice( 0, TAG_NAME_LIMIT );
 
 // Mailchimp — contact sync, not a sender.
 var mailchimp = {
@@ -4964,10 +4988,12 @@ var mailchimp = {
 			// on attaching people to it by name. Both address the same object. The
 			// segment schema says it outright: "The type of segment. Static segments
 			// are now known as tags"
-			// (api.mailchimp.com/schema/3.0/Swagger.json, fetched 2026-09-11).
+			// (api.mailchimp.com/schema/3.0/Definitions/Lists/Segments/Response.json,
+			// fetched 2026-09-12 — the root Swagger.json carries no prose, only $refs
+			// into fragment files like this one).
 			//
-			// IDEMPOTENT ON EVERY PATH: called on create, on rename, on the boot
-			// sweep and on backfill, it converges. That is what lets one hook serve
+			// IDEMPOTENT ON EVERY PATH: called on create, on rename, on a connection
+			// finishing its configuration, and on the backfill migration, it converges. That is what lets one hook serve
 			// all four without a create-vs-update branch anywhere else.
 			register : async ( { connection, context, manifest, settings, token, workflow }, { fetcher, read } = {} ) => {
 
@@ -5033,7 +5059,9 @@ var mailchimp = {
 				// tag-search matches on PREFIX, not on the exact name: "The search
 				// query will be compared to each tag as a prefix, so all tags that
 				// have a name starting with this field will be returned"
-				// (api.mailchimp.com/schema/3.0/Swagger.json, fetched 2026-09-11). So
+				// (api.mailchimp.com/schema/3.0/Parameters/PrefixTagSearchName.json,
+				// fetched 2026-09-12 — the TagSearch path only $refs this parameter, and
+				// the root Swagger.json carries no prose at all). So
 				// "Drawbridge: VIP" answers for "Drawbridge: VIPs" too, and attaching
 				// the row to the first result would point this segment at a different
 				// merchant's tag. The exact name is filtered here.

package/dist/connections/index.d.ts

@@ -3867,6 +3867,13 @@ var klaviyo = {
 				// fetched 2026-09-09).
 				//
 				// IT MERGES, and that is why the blocks below are conditional rather
+				// GROUPED OR FLAT, read as one number. contact.totals.orders and .gross
+				// are { total, conversions, redemptions } now, but a contact the
+				// backfill has not reached still holds the old flat number — and a
+				// naked `totals.orders || 0` would hand Klaviyo the whole object as a
+				// profile property. Klaviyo gets the total either way.
+				const count = ( value ) => typeof value === 'number' ? value : ( value?.total || 0 );
+
 				// than defaulted. "Not including a field in your request will leave it
 				// unchanged" — so omitting the totals on a lead.insert preserves
 				// whatever the last segment run published, where sending zeros would
@@ -3884,13 +3891,13 @@ var klaviyo = {
 										drawbridge_campaigns : ( person.campaigns || [] ).length,
 										drawbridge_draws : totals.draws || 0,
 										drawbridge_entries : totals.entries || 0,
-										drawbridge_orders : totals.orders || 0,
+										drawbridge_orders : count( totals.orders ),
 										// Campaign-attributed, NOT lifetime. A merchant running
 										// Shopify already has lifetime revenue in Klaviyo through
 										// Klaviyo's own integration; what only we can say is how
 										// much a campaign drove. Named so the two cannot be
 										// mistaken for one another in a segment builder.
-										drawbridge_revenue : totals.gross || 0
+										drawbridge_revenue : count( totals.gross )
 									}),
 									// THE DRAWBRIDGE SEGMENTS THEY ARE IN, as a list property the
 									// merchant builds Klaviyo segments on top of. Klaviyo owns no
@@ -4616,7 +4623,24 @@ const subscriberHash = ( email ) => createHash( 'md5' )
 // THE TAG'S NAME, and the one place it is spelled. The member write and the
 // register hook must agree character for character — they address the same
 // object, one by name and one by id — so a prefix change is one edit here.
-const tagName = ( title ) => 'Drawbridge: ' + title;
+//
+// TRUNCATED TO 100, because that is Mailchimp's documented ceiling for a tag
+// name ("Tag names can be a maximum of 100 characters",
+// mailchimp.com/help/create-add-remove-tags, fetched 2026-09-12) and a segment
+// title can be 100 on its own — so the prefix pushes any title over 88 past it.
+// The limit is in their help centre and NOT in the API schema, which constrains
+// `name` to a bare string, so what the API does with an over-long name is
+// unspecified: it may reject the whole write or truncate server-side, and a
+// server-side truncation is the worse outcome because register would then look
+// for a name Mailchimp had silently changed.
+//
+// ponytail: two segments whose first 88 characters match would share one tag.
+// The upgrade is to append a short hash of the segment id, which costs the name
+// its readability in the merchant's own audience — not worth it until somebody
+// actually collides.
+const TAG_NAME_LIMIT = 100;
+
+const tagName = ( title ) => ( 'Drawbridge: ' + title ).slice( 0, TAG_NAME_LIMIT );
 
 // Mailchimp — contact sync, not a sender.
 var mailchimp = {
@@ -4964,10 +4988,12 @@ var mailchimp = {
 			// on attaching people to it by name. Both address the same object. The
 			// segment schema says it outright: "The type of segment. Static segments
 			// are now known as tags"
-			// (api.mailchimp.com/schema/3.0/Swagger.json, fetched 2026-09-11).
+			// (api.mailchimp.com/schema/3.0/Definitions/Lists/Segments/Response.json,
+			// fetched 2026-09-12 — the root Swagger.json carries no prose, only $refs
+			// into fragment files like this one).
 			//
-			// IDEMPOTENT ON EVERY PATH: called on create, on rename, on the boot
-			// sweep and on backfill, it converges. That is what lets one hook serve
+			// IDEMPOTENT ON EVERY PATH: called on create, on rename, on a connection
+			// finishing its configuration, and on the backfill migration, it converges. That is what lets one hook serve
 			// all four without a create-vs-update branch anywhere else.
 			register : async ( { connection, context, manifest, settings, token, workflow }, { fetcher, read } = {} ) => {
 
@@ -5033,7 +5059,9 @@ var mailchimp = {
 				// tag-search matches on PREFIX, not on the exact name: "The search
 				// query will be compared to each tag as a prefix, so all tags that
 				// have a name starting with this field will be returned"
-				// (api.mailchimp.com/schema/3.0/Swagger.json, fetched 2026-09-11). So
+				// (api.mailchimp.com/schema/3.0/Parameters/PrefixTagSearchName.json,
+				// fetched 2026-09-12 — the TagSearch path only $refs this parameter, and
+				// the root Swagger.json carries no prose at all). So
 				// "Drawbridge: VIP" answers for "Drawbridge: VIPs" too, and attaching
 				// the row to the first result would point this segment at a different
 				// merchant's tag. The exact name is filtered here.

package/dist/connections/index.js

@@ -3261,6 +3261,7 @@ var klaviyo_default2 = {
         if (!email) return { message: "That lead has no email address to sync.", skipped: true };
         const person = (context == null ? void 0 : context.contact) || null;
         const totals = (person == null ? void 0 : person.totals) || {};
+        const count = (value) => typeof value === "number" ? value : (value == null ? void 0 : value.total) || 0;
         const profile = await api2("/profile-import", {
           fetcher,
           method: "POST",
@@ -3274,13 +3275,13 @@ var klaviyo_default2 = {
                     drawbridge_campaigns: (person.campaigns || []).length,
                     drawbridge_draws: totals.draws || 0,
                     drawbridge_entries: totals.entries || 0,
-                    drawbridge_orders: totals.orders || 0,
+                    drawbridge_orders: count(totals.orders),
                     // Campaign-attributed, NOT lifetime. A merchant running
                     // Shopify already has lifetime revenue in Klaviyo through
                     // Klaviyo's own integration; what only we can say is how
                     // much a campaign drove. Named so the two cannot be
                     // mistaken for one another in a segment builder.
-                    drawbridge_revenue: totals.gross || 0
+                    drawbridge_revenue: count(totals.gross)
                   },
                   // THE DRAWBRIDGE SEGMENTS THEY ARE IN, as a list property the
                   // merchant builds Klaviyo segments on top of. Klaviyo owns no
@@ -3785,7 +3786,8 @@ var api3 = async (path, { dc, fetcher = fetch, method = "GET", payload, token })
   return response.status === 204 ? null : response.json();
 };
 var subscriberHash = (email) => createHash2("md5").update(String(email).trim().toLowerCase()).digest("hex");
-var tagName = (title) => "Drawbridge: " + title;
+var TAG_NAME_LIMIT = 100;
+var tagName = (title) => ("Drawbridge: " + title).slice(0, TAG_NAME_LIMIT);
 var mailchimp_default2 = {
   // OAUTH 2, authorization code. Every url below is quoted from
   // mailchimp.com/developer/marketing/guides/access-user-data-oauth-2/ rather
@@ -4010,10 +4012,12 @@ var mailchimp_default2 = {
       // on attaching people to it by name. Both address the same object. The
       // segment schema says it outright: "The type of segment. Static segments
       // are now known as tags"
-      // (api.mailchimp.com/schema/3.0/Swagger.json, fetched 2026-09-11).
+      // (api.mailchimp.com/schema/3.0/Definitions/Lists/Segments/Response.json,
+      // fetched 2026-09-12 — the root Swagger.json carries no prose, only $refs
+      // into fragment files like this one).
       //
-      // IDEMPOTENT ON EVERY PATH: called on create, on rename, on the boot
-      // sweep and on backfill, it converges. That is what lets one hook serve
+      // IDEMPOTENT ON EVERY PATH: called on create, on rename, on a connection
+      // finishing its configuration, and on the backfill migration, it converges. That is what lets one hook serve
       // all four without a create-vs-update branch anywhere else.
       register: async ({ connection: connection2, context, manifest, settings, token, workflow }, { fetcher, read } = {}) => {
         var _a;

package/dist/providers.cjs

@@ -3246,6 +3246,7 @@ var klaviyo_default2 = {
         if (!email) return { message: "That lead has no email address to sync.", skipped: true };
         const person = (context == null ? void 0 : context.contact) || null;
         const totals = (person == null ? void 0 : person.totals) || {};
+        const count = (value) => typeof value === "number" ? value : (value == null ? void 0 : value.total) || 0;
         const profile = await api2("/profile-import", {
           fetcher,
           method: "POST",
@@ -3259,13 +3260,13 @@ var klaviyo_default2 = {
                     drawbridge_campaigns: (person.campaigns || []).length,
                     drawbridge_draws: totals.draws || 0,
                     drawbridge_entries: totals.entries || 0,
-                    drawbridge_orders: totals.orders || 0,
+                    drawbridge_orders: count(totals.orders),
                     // Campaign-attributed, NOT lifetime. A merchant running
                     // Shopify already has lifetime revenue in Klaviyo through
                     // Klaviyo's own integration; what only we can say is how
                     // much a campaign drove. Named so the two cannot be
                     // mistaken for one another in a segment builder.
-                    drawbridge_revenue: totals.gross || 0
+                    drawbridge_revenue: count(totals.gross)
                   },
                   // THE DRAWBRIDGE SEGMENTS THEY ARE IN, as a list property the
                   // merchant builds Klaviyo segments on top of. Klaviyo owns no
@@ -3770,7 +3771,8 @@ var api3 = async (path, { dc, fetcher = fetch, method = "GET", payload, token })
   return response.status === 204 ? null : response.json();
 };
 var subscriberHash = (email) => (0, import_node_crypto5.createHash)("md5").update(String(email).trim().toLowerCase()).digest("hex");
-var tagName = (title) => "Drawbridge: " + title;
+var TAG_NAME_LIMIT = 100;
+var tagName = (title) => ("Drawbridge: " + title).slice(0, TAG_NAME_LIMIT);
 var mailchimp_default2 = {
   // OAUTH 2, authorization code. Every url below is quoted from
   // mailchimp.com/developer/marketing/guides/access-user-data-oauth-2/ rather
@@ -3995,10 +3997,12 @@ var mailchimp_default2 = {
       // on attaching people to it by name. Both address the same object. The
       // segment schema says it outright: "The type of segment. Static segments
       // are now known as tags"
-      // (api.mailchimp.com/schema/3.0/Swagger.json, fetched 2026-09-11).
+      // (api.mailchimp.com/schema/3.0/Definitions/Lists/Segments/Response.json,
+      // fetched 2026-09-12 — the root Swagger.json carries no prose, only $refs
+      // into fragment files like this one).
       //
-      // IDEMPOTENT ON EVERY PATH: called on create, on rename, on the boot
-      // sweep and on backfill, it converges. That is what lets one hook serve
+      // IDEMPOTENT ON EVERY PATH: called on create, on rename, on a connection
+      // finishing its configuration, and on the backfill migration, it converges. That is what lets one hook serve
       // all four without a create-vs-update branch anywhere else.
       register: async ({ connection: connection2, context, manifest, settings, token, workflow }, { fetcher, read } = {}) => {
         var _a;

package/dist/providers.js

@@ -3197,6 +3197,7 @@ var klaviyo_default2 = {
         if (!email) return { message: "That lead has no email address to sync.", skipped: true };
         const person = (context == null ? void 0 : context.contact) || null;
         const totals = (person == null ? void 0 : person.totals) || {};
+        const count = (value) => typeof value === "number" ? value : (value == null ? void 0 : value.total) || 0;
         const profile = await api2("/profile-import", {
           fetcher,
           method: "POST",
@@ -3210,13 +3211,13 @@ var klaviyo_default2 = {
                     drawbridge_campaigns: (person.campaigns || []).length,
                     drawbridge_draws: totals.draws || 0,
                     drawbridge_entries: totals.entries || 0,
-                    drawbridge_orders: totals.orders || 0,
+                    drawbridge_orders: count(totals.orders),
                     // Campaign-attributed, NOT lifetime. A merchant running
                     // Shopify already has lifetime revenue in Klaviyo through
                     // Klaviyo's own integration; what only we can say is how
                     // much a campaign drove. Named so the two cannot be
                     // mistaken for one another in a segment builder.
-                    drawbridge_revenue: totals.gross || 0
+                    drawbridge_revenue: count(totals.gross)
                   },
                   // THE DRAWBRIDGE SEGMENTS THEY ARE IN, as a list property the
                   // merchant builds Klaviyo segments on top of. Klaviyo owns no
@@ -3721,7 +3722,8 @@ var api3 = async (path, { dc, fetcher = fetch, method = "GET", payload, token })
   return response.status === 204 ? null : response.json();
 };
 var subscriberHash = (email) => createHash2("md5").update(String(email).trim().toLowerCase()).digest("hex");
-var tagName = (title) => "Drawbridge: " + title;
+var TAG_NAME_LIMIT = 100;
+var tagName = (title) => ("Drawbridge: " + title).slice(0, TAG_NAME_LIMIT);
 var mailchimp_default2 = {
   // OAUTH 2, authorization code. Every url below is quoted from
   // mailchimp.com/developer/marketing/guides/access-user-data-oauth-2/ rather
@@ -3946,10 +3948,12 @@ var mailchimp_default2 = {
       // on attaching people to it by name. Both address the same object. The
       // segment schema says it outright: "The type of segment. Static segments
       // are now known as tags"
-      // (api.mailchimp.com/schema/3.0/Swagger.json, fetched 2026-09-11).
+      // (api.mailchimp.com/schema/3.0/Definitions/Lists/Segments/Response.json,
+      // fetched 2026-09-12 — the root Swagger.json carries no prose, only $refs
+      // into fragment files like this one).
       //
-      // IDEMPOTENT ON EVERY PATH: called on create, on rename, on the boot
-      // sweep and on backfill, it converges. That is what lets one hook serve
+      // IDEMPOTENT ON EVERY PATH: called on create, on rename, on a connection
+      // finishing its configuration, and on the backfill migration, it converges. That is what lets one hook serve
       // all four without a create-vs-update branch anywhere else.
       register: async ({ connection: connection2, context, manifest, settings, token, workflow }, { fetcher, read } = {}) => {
         var _a;

package/package.json

@@ -226,5 +226,5 @@
     "prepublishOnly": ". \"$HOME/.nvm/nvm.sh\" && nvm use && tsup && node --test"
   },
   "types": "dist/index.d.ts",
-  "version": "0.0.169"
+  "version": "0.0.170"
 }