salesforce-core-workflow-a
Execute Salesforce CRUD operations on standard sObjects with SOQL and REST API. Use when creating, reading, updating, or deleting Accounts, Contacts, Leads, or Opportunities via the Salesforce API. Trigger with phrases like "salesforce CRUD", "salesforce create record", "salesforce update account", "salesforce SOQL query", "salesforce REST API".
Best use case
salesforce-core-workflow-a is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Execute Salesforce CRUD operations on standard sObjects with SOQL and REST API. Use when creating, reading, updating, or deleting Accounts, Contacts, Leads, or Opportunities via the Salesforce API. Trigger with phrases like "salesforce CRUD", "salesforce create record", "salesforce update account", "salesforce SOQL query", "salesforce REST API".
Teams using salesforce-core-workflow-a should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/salesforce-core-workflow-a/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How salesforce-core-workflow-a Compares
| Feature / Agent | salesforce-core-workflow-a | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Execute Salesforce CRUD operations on standard sObjects with SOQL and REST API. Use when creating, reading, updating, or deleting Accounts, Contacts, Leads, or Opportunities via the Salesforce API. Trigger with phrases like "salesforce CRUD", "salesforce create record", "salesforce update account", "salesforce SOQL query", "salesforce REST API".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Salesforce Core Workflow A — CRUD & SOQL
## Overview
Primary workflow: perform CRUD operations on standard sObjects (Account, Contact, Lead, Opportunity) using SOQL queries, jsforce methods, and REST API endpoints.
## Prerequisites
- Completed `salesforce-install-auth` setup
- jsforce installed and connection configured
- Understanding of Salesforce sObject model
## Instructions
### Step 1: SOQL Queries (Read Operations)
```typescript
import { getConnection } from './salesforce/connection';
const conn = await getConnection();
// Basic query — all open opportunities closing this quarter
const opps = await conn.query(`
SELECT Id, Name, Amount, StageName, CloseDate, Account.Name
FROM Opportunity
WHERE IsClosed = false
AND CloseDate = THIS_QUARTER
ORDER BY Amount DESC
LIMIT 50
`);
// Relationship query — Accounts with their Contacts
const accountsWithContacts = await conn.query(`
SELECT Id, Name, Industry,
(SELECT Id, FirstName, LastName, Email FROM Contacts)
FROM Account
WHERE Industry = 'Technology'
LIMIT 20
`);
// Aggregate query
const revByIndustry = await conn.query(`
SELECT Industry, COUNT(Id) numAccounts, SUM(AnnualRevenue) totalRevenue
FROM Account
WHERE Industry != null
GROUP BY Industry
ORDER BY SUM(AnnualRevenue) DESC
`);
// SOSL search — full-text search across objects
const searchResults = await conn.search(
`FIND {Acme} IN ALL FIELDS RETURNING
Account(Id, Name, Industry),
Contact(Id, FirstName, LastName, Email),
Lead(Id, Name, Company, Status)`
);
```
### Step 2: Create Records
```typescript
// Single record create via sObject
const newLead = await conn.sobject('Lead').create({
FirstName: 'Jane',
LastName: 'Smith',
Company: 'Acme Corp',
Email: 'jane.smith@acme.example.com',
Status: 'Open - Not Contacted',
LeadSource: 'Web',
});
console.log('Lead ID:', newLead.id); // '00Qxx...'
// Create with relationship (Contact linked to Account)
const newContact = await conn.sobject('Contact').create({
FirstName: 'John',
LastName: 'Doe',
Email: 'john.doe@example.com',
AccountId: '001xxxxxxxxxxxx', // Existing Account ID
Title: 'VP Engineering',
});
// Create Opportunity with all key fields
const newOpp = await conn.sobject('Opportunity').create({
Name: 'Acme Corp — Enterprise License',
AccountId: '001xxxxxxxxxxxx',
StageName: 'Prospecting',
CloseDate: '2026-06-30',
Amount: 50000,
});
```
### Step 3: Bulk Create with sObject Collections
```typescript
// Create up to 200 records in a single API call (sObject Collections)
const contacts = [
{ FirstName: 'Alice', LastName: 'A', Email: 'alice@example.com', AccountId: '001xx' },
{ FirstName: 'Bob', LastName: 'B', Email: 'bob@example.com', AccountId: '001xx' },
{ FirstName: 'Carol', LastName: 'C', Email: 'carol@example.com', AccountId: '001xx' },
];
const results = await conn.sobject('Contact').create(contacts);
// Returns array: [{ id: '003xx', success: true }, ...]
// Check for partial failures
for (const result of results) {
if (!result.success) {
console.error('Failed:', result.errors);
}
}
```
### Step 4: Update Records
```typescript
// Single update
await conn.sobject('Opportunity').update({
Id: '006xxxxxxxxxxxx',
StageName: 'Qualification',
Amount: 75000,
Description: 'Upgraded after demo call',
});
// Bulk update (up to 200)
const updates = [
{ Id: '003xx1', Title: 'Senior Engineer' },
{ Id: '003xx2', Title: 'Staff Engineer' },
{ Id: '003xx3', Title: 'Principal Engineer' },
];
await conn.sobject('Contact').update(updates);
```
### Step 5: Upsert (Insert or Update by External ID)
```typescript
// Upsert uses an External ID field to match existing records
// Requires a custom External ID field on the sObject
await conn.sobject('Account').upsert({
External_ID__c: 'EXT-12345', // Custom external ID field
Name: 'Acme Corporation',
Industry: 'Technology',
Website: 'https://acme.example.com',
}, 'External_ID__c'); // Field to match on
```
### Step 6: Delete Records
```typescript
// Single delete
await conn.sobject('Lead').destroy('00Qxxxxxxxxxxxx');
// Bulk delete (up to 200)
const idsToDelete = ['00Qxx1', '00Qxx2', '00Qxx3'];
await conn.sobject('Lead').destroy(idsToDelete);
```
### Step 7: Direct REST API Calls
```typescript
// When jsforce doesn't wrap what you need, use raw REST
// GET — describe an sObject
const accountMeta = await conn.request(
'/services/data/v59.0/sobjects/Account/describe'
);
console.log('Fields:', accountMeta.fields.map((f: any) => f.name));
// POST — create via REST
const created = await conn.request({
method: 'POST',
url: '/services/data/v59.0/sobjects/Account/',
body: JSON.stringify({ Name: 'REST Created Account' }),
headers: { 'Content-Type': 'application/json' },
});
// PATCH — update via REST
await conn.request({
method: 'PATCH',
url: `/services/data/v59.0/sobjects/Account/${created.id}`,
body: JSON.stringify({ Industry: 'Consulting' }),
headers: { 'Content-Type': 'application/json' },
});
```
## Output
- SOQL queries returning typed sObject records
- Single and bulk record creation
- Record updates and upserts by External ID
- Record deletion (single and bulk)
- Direct REST API calls for advanced use cases
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| `INVALID_FIELD` | Wrong field API name in SOQL | Use Object Manager to check field names |
| `REQUIRED_FIELD_MISSING` | Create missing required fields | Check Setup > Object Manager > Fields for required |
| `DUPLICATE_VALUE` | Unique field constraint violated | Check External ID or unique field values |
| `INSUFFICIENT_ACCESS_OR_READONLY` | Missing object/field permissions | Check Profile or Permission Set assignments |
| `UNABLE_TO_LOCK_ROW` | Concurrent update on same record | Retry with backoff — common in high-volume writes |
| `ENTITY_IS_DELETED` | Operating on deleted record | Query Recycle Bin or use `ALL ROWS` in SOQL |
## Resources
- [sObject CRUD (REST API)](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_sobject_create.htm)
- [sObject Collections](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_composite_sobjects_collections.htm)
- [SOQL Reference](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm)
- [SOSL Reference](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_sosl.htm)
## Next Steps
For Bulk API and Composite API patterns, see `salesforce-core-workflow-b`.Related Skills
calendar-to-workflow
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
workhuman-core-workflow-b
Workhuman core workflow b for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow b".
workhuman-core-workflow-a
Workhuman core workflow a for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow a".
wispr-core-workflow-b
Wispr Flow core workflow b for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow b".
wispr-core-workflow-a
Wispr Flow core workflow a for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow a".
windsurf-core-workflow-b
Execute Windsurf's secondary workflow: Workflows, Memories, and reusable automation. Use when creating reusable Cascade workflows, managing persistent memories, or automating repetitive development tasks. Trigger with phrases like "windsurf workflow", "windsurf automation", "windsurf memories", "cascade workflow", "windsurf slash command".
windsurf-core-workflow-a
Execute Windsurf's primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature".
webflow-core-workflow-b
Execute Webflow secondary workflows — Sites management, Pages API, Forms submissions, Ecommerce (products/orders/inventory), and Custom Code via the Data API v2. Use when managing sites, reading pages, handling form data, or working with Webflow Ecommerce products and orders. Trigger with phrases like "webflow sites", "webflow pages", "webflow forms", "webflow ecommerce", "webflow products", "webflow orders".
webflow-core-workflow-a
Execute the primary Webflow workflow — CMS content management: list collections, CRUD items, publish items, and manage content lifecycle via the Data API v2. Use when working with Webflow CMS collections and items, managing blog posts, team members, or any dynamic content. Trigger with phrases like "webflow CMS", "webflow collections", "webflow items", "create webflow content", "manage webflow CMS", "webflow content management".
veeva-core-workflow-b
Veeva Vault core workflow b for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow b".
veeva-core-workflow-a
Veeva Vault core workflow a for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow a".
vastai-core-workflow-b
Execute Vast.ai secondary workflow: multi-instance orchestration, spot recovery, and cost optimization. Use when running distributed training, handling spot preemption, or optimizing GPU spend across multiple instances. Trigger with phrases like "vastai distributed training", "vastai spot recovery", "vastai multi-gpu", "vastai cost optimization".