Skip to main content

Create your first Agent Memory

Use a manual memory when your team already knows a rule and wants Clerked to apply it on future work. Write one behavior at a time. A concrete rule is easier to review and less likely to affect unrelated vendors.

Add a memory​

  1. In the left sidebar, click Agents.
  2. Open Invoice processing or Email processing. If you are working on a custom agent, open it and select Memories.
  3. In the Memories section, click Add memory.
  4. In the editor, describe what the agent should remember. Include the trigger, the action, and any exception. For example: “For Acme's freight lines, use the Freight account unless the PO has a project allocation.”
  5. Choose Global or Vendor in Memory scope. If you choose Vendor, select the vendor that owns the rule.
  6. Select Add memory.

After the request finishes, the new row appears as active. Its provenance shows Created by and the author name. The agent can use it on later invoice or email processing; it does not change a record that has already completed.

If the same rule belongs to several suppliers, add the vendor references that belong with it instead of writing several almost-identical Global rules. Check the visible scope and record chips before saving, then find the finished row in the list to confirm its attribution.

Type @ in the editor to find a vendor, account, or PO. Use a link when the rule depends on a specific record. The linked name gives reviewers a quick way to distinguish “use this account for every vendor” from “use this account for one vendor's freight line.”

Do not paste a raw record ID into the memory. If the record cannot be found, write the visible name and ask an admin to check that the reference is available in your company schema.

Make the wording safe to reuse​

  • Say when the rule applies.
  • Name the field or action the agent should take.
  • State the exception that should prevent the rule from applying.
  • Keep unrelated vendor rules in separate memories.
  • Choose Vendor scope for a vendor-only rule instead of burying the vendor name in a Global memory.

For the difference between rule, procedural, and preference memories, see Memory types. For the effect of each anchor, see Memory scope.

Edit or archive a memory​

Find the row in Memories, then select Edit to correct its guidance or Archive memory to stop it from being retrieved. Review the scope before you save an edit. If the rule was proposed from a correction rather than written by you, use the Tasks review flow so its evidence and decision remain together.

An archived memory stays visible on the Archived tab for 30 days. The tab is read-only: you can open the row to read its full text, but there is no restore action and no editing there. If you archived a rule by mistake, copy its text from the Archived tab and add it again as a new memory.

Permission required

The Agents page and memory actions are permission-gated. If Add memory or the edit controls are missing, ask a company administrator to grant the memory permission or make the change for you.

We use cookies to understand how visitors use our site.