feat(library): How Do You Build a Salesforce AI Lead-Scoring Agent With Sim?

[icecrasher321]

Summary

• Adds the library post "How Do You Build a Salesforce AI Lead-Scoring Agent With Sim?" at apps/sim/content/library/salesforce-ai-agent-lead-scoring-workflow/.
• Generated by the Library Post PR Maker workflow from a Gauge Action Center brief.

Type of Change

• New content

Testing

Not built or tested locally. After the PR opens, the workflow's content gate checks changed paths, frontmatter keys, FAQ placement, and internal links; CI check:library-content validates the post once it is enabled.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[icecrasher321]

@cubic review

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 8, 2026 5:00pm UTC

[icecrasher321]

@greptile

[cubic-dev-ai]

@cubic review

@icecrasher321 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[Low risk] Adds a tutorial document and cover image to the library.

The revised guide appears safe to merge.

What we checked:

• Named fields can be updated: The tool sends Status, LeadSource, Title, and Description to Salesforce.

Summary

Adds a Salesforce lead-scoring guide and cover image.

• Separates model evidence from fixed scoring rules and human approval.
• Corrects all three previous findings: custom scores need a separate write path, native Task creation cannot choose an owner, and record tests now use reachable scores.
• No new actionable issues found in the changes since the previous review.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Retrieve leads] --> B[Extract evidence]
  B --> C[Calculate score and tier]
  C --> D[Review when required]
  D --> E{Approved?}
  E -->|No| F[Stop without Salesforce writes]
  E -->|Yes| G[Check for an existing task]
  G --> H[Apply supported writes]
  H --> I[Verify Salesforce results]
  C --> J[Retain execution evidence]

Loading

_{Reviews (2) · Last reviewed commit: "Pi Babysit: address PR #8804 feedback" · Reviewed by Greptile}

[icecrasher321]

@cubic review

[icecrasher321]

@greptile

[cubic-dev-ai]

@cubic review

@icecrasher321 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}