Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Editing, publishing and deleting

What you can change on a connector your workspace owns: editing it, credential verification, adding actions, publishing versions and deleting it.

Everything on this page applies to connectors your workspace owns: ones you created from the Create connector menu or brought in with Import from file. Their card is badged Custom and reads Managed by followed by your organization's name. Managed connectors (badged managed, Managed by Fastn) are read-only in your workspace; to change one of their actions, use Propose an update.

Where the controls are

On an owned connector:

  • the header's ⋯ menu holds Edit and Delete;

  • the connector's row in the rail has + (Add action) and a ⋯ menu with New Folder, Import, Export All, Connect, Edit and Delete;

  • the catalog card's ⋯ menu holds Select, Edit, Export and Delete (see Importing and exporting);

  • each test version under Overview → Versions has Publish to live.

Edit a connector

⋯ → Edit opens Edit connector. It has the same Identity, Connection and Authentication sections as Create a connector, plus Credential verification:

Runs when someone connects, so a wrong API key is caught immediately instead of failing later in a workflow. Required before this connector can go live.

Field
Meaning

Verification action

An action fastn runs right after someone connects, to prove the credential works. Only read-only actions with no required inputs can be used. The default, None - connections stay unverified, skips the check.

Success path

Optional. A field that must be present in the response. Use this when the provider answers bad credentials with 200 and a login page. For example $.id.

Save changes saves. The footer explains where the change goes: Changes apply to the test version until you publish.

Add an action

+ next to the connector's name in the rail opens a blank action in the editor:

  1. Replace New Action with the action's name, and add a description.

  2. Choose the method and enter the URL. You can also paste a complete curl command into the URL field.

  3. Fill in the tabs as described in Actions.

  4. Click Create Action. Discard throws the draft away.

The action's slug is derived from its name in camelCase, for example List Users becomes listUsers, and the action opens at /integrations/connectors/<connector-slug>/<action-slug>. After that, edit it in the same editor and click Save Changes.

Actions can also be grouped into folders (⋯ → New Folder on the connector's rail row).

Publish a version

Every saved change goes to the connector's Test version. Customers keep running the Live version until you publish.

  1. Open Overview and scroll to Versions, with Test selected.

  2. Click Publish to live on the version.

  3. Confirm:

Customers pinned to another version (see Version pins) stay on it. The Edit dialog also says credential verification is required before this connector can go live. Publishing a test version without it is not blocked, so add a verification action before customers rely on the connector.

Restore a version

Each save adds a version with a note of what changed, for example Updated description, authMethods. Older versions in the Versions list have a Restore button.

This will restore the connector configuration to this version and create a new test version. You can then publish when ready.

Restore Version confirms. Customers are not affected until you publish the new test version.

Delete a connector

⋯ → Delete opens Delete Connector:

  • Soft delete (the default): the connector disappears from the catalog. The dialog says it can be restored. Every connection on it is disconnected and its credentials are deleted; restoring brings back the connector, not the credentials.

  • Permanently delete (cannot be undone): tick this box to remove the connector for good.

After Delete, you return to the catalog.

Last updated

Was this helpful?