pluckBring the useful bits
back to your work.
Six ways to turn “I do this all the time” into a profile. These are illustrative workflows you can configure for your own approved sites and services.
Fill in the missing details.
Start with a company name. Bring the information from an approved directory or internal service into your customer record.
- Choose a manually entered company name or a value scraped from your CRM.
- Configure the lookup and select the company, email, and location fields.
- Review the results, then drag each card or fill mapped fields.
An answer behind every order ID.
Give a support page a route to the order details you keep opening another tab to find.
- Read the order reference from the support page with a selector.
- Look it up on your order website, using saved click and wait steps.
- Bring back a tracking reference and delivery status; compare before filling.
Turn the whole list into results.
When the same lookup repeats, use Batch to run a manual-input profile for each reference.
- Paste one value per line: up to 5 on Free or 500 on Pro.
- Choose a pause between runs and review the success or failure of each row.
- Copy the results table, download CSV, or load an individual row into Results.
Give product data a tidy landing.
Bring product names, reference codes, or prices from a configured source into an admin form.
- Use a SKU as the lookup value.
- Extract each field and apply basic text clean-up, or use Pro for regex replacement and date conversions.
- Review differences and drag results into the destination fields.
An endpoint becomes a side panel.
Use a service you control or have permission to access. Pluck can send a request and turn JSON response values into cards.
- Configure a GET webhook on Free, or use Pro for authentication, request bodies, and other supported HTTP methods.
- Send a test request and browse the response to choose JSON paths.
- Map those values to your form or leave them as draggable cards.
Describe the detail you need.
When a page’s useful information is buried in prose, optional AI extraction can return named values for review.
- Choose local Ollama on Free, or connect a cloud provider with Pro, then select a model.
- Describe the fields, choose the page or a region, and consent for cloud extraction.
- Inspect the returned values and their evidence before using them.
These examples are recipes, not bundled integrations. Automatic page-triggered lookups and profile switching require Pro. See Free and Pro allowances. Website structure, access permissions, authentication, and field compatibility determine what each profile can do.
Configure. Open.
A little magic. Save.
Pluck is being prepared for Chrome. In the meantime, take the interactive demo for a spin.
Chrome 121 or later · Web Store link coming soon