Edit

Edit covers changes to things that already exist — a deployed automation needs another step, a connector needs a new endpoint, a vendor renamed a field and the catalog has to catch up.

Skills in this category

• Edit an automation — modify a committed automation. Add a step, change a mapping, swap a service for another, retitle, disable a branch.
• Edit a trigger, action, or connector — modify an existing assembly. Update for a vendor's API change, add a new operation, retire an old one, fix a trigger payload shape.

Edits never touch the running automation in place. Claude loads the committed version into a draft workspace, applies the change there, and asks whether you want to overwrite the original or save the result as a copy before committing.

Edit an automation

Edits to automations can start with either side. You describe a change in plain language and Claude makes it; or Claude initiates — an automation alerts on a failure in production, a pattern-library refinement needs to propagate to existing automations, or a test points at a logic bug. Either way, Claude loads the current version, applies the change, and shows the result.

> Add a step that posts the new contact to a Slack channel.
> Lowercase the email address before sending it to Mailchimp.
> Disable the duplicate-check branch for now.

Before committing, Claude asks whether to overwrite the original automation or save the edits as a copy. Each commit is a numbered version with a description, so the previous version is always recoverable from version history in the automation editor.

Edit a trigger, action, or connector

Edits to triggers, actions, and connectors usually start with Claude. An automation fails in production, the diagnosis points at the trigger or action that broke, Claude proposes the fix. Sometimes you initiate explicitly — a vendor sent a field-rename notice, you need an operation that doesn't exist yet, or a webhook payload changed shape.

> Salesforce renamed `email_address` to `Email__c`. Update the contact connector.
> Add a DELETE operation to the HubSpot Companies connector.
> The HubSpot `findCompany` operation is deprecated. Route it to `searchCompanies`.

In either case: Claude loads the assembly, makes the change, recompiles, and tests it — a real API call for an action, payload parsing for a trigger, a connection test for a connector. If the test fails, Claude reads the error, fixes the code, and retries.

See also

• Test & Deploy — verify and promote
• Convert Assembly — for legacy connectors that need a structural conversion before they can be safely edited