Skip to content
Act

Configure it once
Stop running it by hand

Jobs and actions run on a schedule, the moment a record changes, or straight from your own code. Nobody has to start them.

Take a product tourBook a demo

What changes when the fix runs inside the automation

Before Plauti

  • An integration inserts a second record for a customer who already exists, and nobody notices until a report is wrong.
  • The nightly cleanup is a job someone remembers to run, or doesn't.
  • Correcting a field on 3,000 records means an export, a spreadsheet and a re-import.
  • Your automation can create and update records, but has no way to tell whether the data it just wrote is any good.

WithPlauti

  • The incoming record is scored against existing ones as it lands, and merged on arrival above the threshold you set.
  • The same job runs on a set cadence and reports what it changed in the job overview.
  • A filter defines the set and the action runs in the background, in batches, inside the platform's own processing limits.
  • Dedupe, verification and field actions are steps in that automation, called like any other.

One configured action, every way to start it

Configure what an action does once. Where it runs from is a separate choice, and you can make it more than once.

  • On a schedule

    Put a job or macro on a daily, weekly, monthly or custom schedule. Pause it, edit it, or run it once from the schedule overview.

  • From a report or list view

    Add a launcher to any list view and fix the records that need attention there. Or turn a saved report into a work list and action everything on it.

  • Straight from automation

    Apply an action every time a record is created, updated or restored, whether by a person, an import, a web form or an API call. Filtered to the records you target, fully logged, no review queue.

  • Trigger anything via Apex/REST API & plugins

    Search, merge, convert and trigger indexing from your own back-end, using the scenarios your admins configured. Plugins hook your own logic into search, merge and convert.

  • Ask AI

    Summarize cases, draft emails, enrich records. The answer is written back into a field you choose, and you pick the provider and the prompts.

Safe to switch on.

  • Who can run what

    Control which profiles can launch which actions, and on which objects.

    • Access per action, per object, per profile.
    • A record cap per profile or user.

  • Auditable

    Every run is logged, and what it changed can be rolled back.

    • Action log: what ran, who started it, when.
    • Record log: which records changed, and what changed.

Watch a job run itself.

Interactive product tours. No install, no sales call.

More product tours

Customer quote

Automated cleansing

“The time saved cleaning up duplicate entries and mass editing/deleting records. Direct Processing with cross-object functionality is a game-changer.”
Options Technology logo

Roger Rooney — VP Operations

Options Technology

Options Technology

Frequently asked questions

Can I put a data quality job on a schedule?

Yes. Jobs and saved macros can run once at a future time, or on a recurring cadence: daily, weekly, monthly or a schedule you define. Scheduled runs use the same processing engine as manual ones, and their progress, results and errors appear in the same job overview.

Can someone run an action from a report or list view?

Yes. Add a launcher to any standard or custom list view and action the records you select there, or turn a saved report into a work list instead. The same launcher appears on the action grid and on duplicate and validation job results.

Is there a job report or audit trail?

Both. Each job has an overview with progress while it runs and results when it finishes, with errors captured per record so you can see exactly which ones failed and why. Separately, every action run from a list view or a job is written to an audit log at action level, with an optional record-level log of which records changed and what changed.

Can I trigger Plauti from my own code?

Yes. Apex and REST APIs expose duplicate search, matching scores, master-record selection, merges and job starts, so a trigger, a custom component or an external system can call them, using the scenarios and merge rules your admins configured. Plugins register your own classes into search, prevention, merge and convert, and a command-line tool covers CI/CD.

Which AI model does Ask AI use?

The one you choose to connect. Ask AI sends a prompt with field values from the record injected into it and writes the response into a field you choose. You pick the provider: Azure OpenAI, Google Gemini, AWS Bedrock, OpenAI, or your own endpoint. You also set the model, the temperature and the API key, so which model sees your records stays your decision.

See how it works

Talk with one of our experts to see how that works for your use case.

Book a demo