Managing web clipper clip actions
  • 04 Oct 2022
  • 1 Minute to read
  • Dark
    Light

Managing web clipper clip actions

  • Dark
    Light

Adding a clip action created by another collaborator

If one of your collaborators has already set up a clip action in a base for which you have edit access, you can add that clip action to your own browser extension. All you have to do is go to the web clipper extension associated with that clip action and click the Add to extension button. You and your collaborators can use this to share all your clipped content in the same table.

Any changes made to a clip action configuration in a web clipper extension will automatically be reflected in the browser extension for every collaborator who’s added that clip action, keeping your whole team up-to-date with any changes.

Removing clip actions

To remove a previously added clip action from your browser extension, open the browser extension, select a clip action you’d like to remove, open the menu button (the three dots in the upper right-hand corner), and select Remove clip action.

You can remove a clip action from your browser by choosing the Remove clip action from the clip action menu.

Importing and exporting clip actions

When you open up the extension to create a new clip action recipe, you’ll now see the option to import or export the recipe.

The import and export options are at the bottom of the clip action extension configuration.

This will allow you to export a JSON file that reflects your clip action’s “recipe” (i.e. the fields and the CSS selector, if used) or import somebody else’s recipe.

When you import a recipe, you’ll be asked to map each field from the recipe to a field in your table. Make sure that you have the correct field types (e.g. if the original recipe maps a particular value to an attachment field, you’ll need to have an attachment field in your table). Once you’ve mapped the fields, you can load the clip action into the browser extension and you’re ready to go!

The fields that are left to choose will be available in the dropdown while fields not supported or those already mapped will be disabled.

For some examples, check out the community forum here!


Was this article helpful?