Edit and test safely

Change and validate visible connector settings without putting unsaved values into real delivery. Test draft, Restore saved, and Save changes each protect a different boundary.

Why it matters

The draft and saved revision let operations investigate mapping, destination, or credential changes while real deliveries continue to use the last saved active revision. This makes a configuration change deliberate instead of turning every edit into an immediate rollout.

Where to work

Open Company -> Connectors, select Edit for the intended connector, and work in the connector editor and its action bar.

Steps

Confirm the provider badge and current revision before changing the form.
Edit the required fields and review the modified-field markers and unsaved draft count.
Run Test draft with synthetic data when you need a point-in-time response from the values currently visible.
Select Restore saved if the visible changes should be discarded.
Select Save changes when the reviewed values should become the next saved revision.
Activate or Resume only after the intended values are saved; if the form is dirty, save or restore it first.

See it in HoneyFalcon

Step 1 of 4: Saved and Draft state with changed-field markers.

Step 2 of 4: Test draft control and the visible saved-revision boundary.

Step 3 of 4: Restore saved and Save changes decisions.

Step 4 of 4: active state bound to the saved revision.

Know which version each action uses

Keep one provider identity

The provider is selected when the connector is created. Editing a HubSpot connector keeps it a HubSpot connector; create a new connector for another provider so history, health, credentials, and revisions do not become mixed.

Understand the visible draft

Typing changes the visible form only. Modified fields and the action bar show that the draft differs from the saved revision, and navigation warns before unsaved values are abandoned.

Real deliveries do not consume this visible draft.

Use Test draft for one punctual request

Test draft sends synthetic test values using the configuration currently visible in the form. An allowlisted response displays Destination accepted the test together with the HTTP status.

The test does not save or activate the draft, change connector delivery status, exercise real delivery, or create a row in Delivery history.

Choose Restore saved or Save changes

Restore saved reloads the current saved revision without creating a new revision. Use it when the visible experiment should be abandoned.

Save changes validates the complete configuration and creates the next saved revision. If another administrator saved first, reload and review their revision before trying again; write-only secrets must be entered again when required.

Activate only the saved revision

Activate and Resume are separate state actions. They use the current saved revision and remain unavailable while the editor has unsaved changes that must first be saved or restored.

Pause stops new deliveries for the active connector and does not save the visible draft.

Recognize a credential without revealing it

After save, HoneyFalcon shows the provider, Saved state, and a bounded suffix for a normal-length credential. The complete credential is not returned to the page.

Use Replace credential for a new value or Remove credential when the connector should no longer keep one.

A successful Test draft proves only that the visible request received an allowlisted HTTP response at that moment. It does not save, activate, run real delivery, or create Delivery history.

The reviewed revision is ready when

The modified-field markers and unsaved draft count match the changes you intended to review.
Test draft reports only the point-in-time result of the visible form.
Restore saved returns the editor to the current saved revision, or Save changes creates the intended next revision.
Activate or Resume uses a clean saved revision while Delivery history remains unchanged by the draft test.