Kit Campaign Automation — Friction Log & Workflow Fixes

Any PUT /v4/broadcasts/{id} request to a scheduled broadcast silently removes the scheduled send time. The broadcast reverts to "send now" state with no warning. This is a data-loss issue — the schedule disappears without any API error or confirmation.

Affected operations: updating content, changing the subject line, changing the sender — any PUT wipes the schedule.

The Kit email editor rejects any anchor tag with href="tel:..." with the error "Unsupported value 'tel:5414611737' passed to href." This happens in both the visual editor and the Edit HTML modal — there is no way to insert a clickable phone link in a Kit email.

All Kit API calls made via curl or Python from the Claude Cowork sandbox return exit code 56 (network unreachable / connection reset). The sandbox cannot reach api.kit.com. This eliminates all API-driven automation workflows for content updates and scheduling.

Kit's email editor is built on Slate.js with React. Direct manipulation of the DOM (innerHTML, textContent) updates what's visible on screen, but React's internal state still holds the old content. When the Save button is clicked, React serializes its own state — not the DOM — and the edit is lost or rejected.

This is why pasting content via innerHTML appeared to work visually but failed on save, and why a lingering tel: link continued to block saving even after it appeared to be removed from the visible editor.

When document.execCommand('insertHTML', false, html) is called on Kit's Slate.js editor, it simultaneously updates React state correctly AND opens the "Edit HTML" modal overlay. If you click Save inside the modal, Kit validates the HTML again — which may differ from what was inserted.

The Chrome MCP's type action types the literal characters ’ rather than the actual Unicode character (right single quotation mark '). This corrupts any email content with curly quotes, em dashes, or other non-ASCII characters.

// Works — Unicode in JS string literal, not typed
document.execCommand('insertHTML', false,
  '<p>You’re getting this...</p>');

Kit's share page shows a scheduled broadcast's time with an "Unschedule" button but no pencil/edit button to modify just the time. To change the send time, you must: (1) click Unschedule to revert to "Sending now" state, (2) click the pencil icon that appears, (3) reselect the date and time from scratch in the react-datepicker.

When navigating from the draft edit page to the share page (via the "Continue" button or direct URL), Kit automatically saves the current editor state. The "Saved" indicator in the bottom bar confirms the save. There is no need to click a separate Save button before leaving the editor.

The "From address" dropdown and other Kit UI controls do not reliably respond to coordinate-based clicks. The dropdown opens but options don't register, or the click lands outside the target. This is likely due to dynamic positioning and React portal overlays.

When duplicating a CF7 form, the redirect action is not copied. Clicking the "Redirect" option in the "Add Action" dropdown via Chrome MCP JS click does not trigger the AJAX call that injects the action fields into the page. The dropdown closes but no fields appear.

When a CF7 form is duplicated, the new form ID is not automatically added to any existing WP Webhooks Pro webhook triggers. Form submissions from the duplicate silently bypass all Zapier zaps — no error, no log, no delivery.

When trying to locate form inputs via document.elementFromPoint(x, y), the method returns null if the target element is above or below the current viewport — even if the element exists in the DOM. This caused failed element lookups on the CF7 admin form editor.