Salesforce Service Cloud
Salesforce Service Cloud follows the same ActionPlane path: understand the workflow, test it safely, connect a sandbox, and then widen it only after preview, approval, and rollback evidence look credible.
Sandbox availability
Keep the first connector setup constrained to one environment, one identity, and one clearly reviewable workflow.
Get the right sandbox or trial environment
Use a customer-owned sandbox or staging tenant for this connector. Required account type: Customer-owned non-production environment.
Create the connector credentials and initial allowlist
Save the Salesforce login URL, External Client App or Connected App credentials, and the Case allowlist for Status, Priority, and Description.
Enter the connector settings in ActionPlane
Open the connector page in ActionPlane, save the environment URL and credentials, and keep the first workflow narrow enough that the operator can explain every writable field.
Validate auth and sync metadata
Run metadata sync so ActionPlane can validate Salesforce Case fields and writable resolution fields before live writes.
Run the first dry run before any live sandbox write
Submit the Salesforce resolve-case preset as a dry run from the dashboard and confirm that the preview, governance decision, and artifacts look correct.
Business context
Start with one record and one reviewed write path that is easy for both a technical evaluator and a buyer to follow.
Starting record state
The sample record is stable, the allowlist is narrow, and the operator can see the exact fields that are about to change.
Requested change
Apply one deterministic change that produces a visible preview, clear policy outcome, and reversible execution path.
Why it routes
The first sample needs to be explainable without narration, so it should route through the same approval or execution lane you plan to use in production.
Expected artifacts
The sample should leave request evidence, output evidence, and a short audit trail that explains why the run moved forward or stopped.
Reset behavior
Reset should return the sample record to the initial seeded state.
Onboarding metering tracks activation progress for the connector. It is not a separate billable unit; workspace billing remains governed-run based.
Save the connector, validate it immediately, and sync metadata in one authenticated call.
{
"loginUrl": "https://login.salesforce.com",
"clientId": "\u003Cclient-id\u003E",
"clientSecret": "\u003Cclient-secret\u003E",
"refreshToken": "\u003Crefresh-token-or-empty\u003E",
"apiVersion": "66.0",
"isSandbox": true,
"isEnabled": true,
"validateAfterSave": true,
"syncMetadataAfterSave": true,
"managedObjects": [
{
"objectApiName": "Case",
"displayName": "Case",
"allowedFields": [
"Status",
"Priority",
"Description"
]
}
]
}
curl -X POST \ "$ACTIONPLANE_BASE_URL/api/connectors/onboarding/salesforce-service-cloud/connect" \ -H "Authorization: Bearer <session-token>" \ -H "Content-Type: application/json" \ --data @"connect-salesforce-service-cloud.json"
Re-run auth and instance validation without resubmitting the connector payload.
curl -X POST \ "$ACTIONPLANE_BASE_URL/api/connectors/onboarding/salesforce-service-cloud/validate" \ -H "Authorization: Bearer <session-token>" \ -H "Content-Type: application/json"
Refresh the writable object and field catalog after credentials or allowlists change.
curl -X POST \ "$ACTIONPLANE_BASE_URL/api/connectors/onboarding/salesforce-service-cloud/sync-metadata" \ -H "Authorization: Bearer <session-token>" \ -H "Content-Type: application/json"
Visible ticket or case state preview before execution
Connector-aware approval and simulation posture
Audit, evidence, and rollback context attached to the same support run
First-class onboarding API can save, validate, and sync the connector in one authenticated flow
Start with one sandbox record or ticket that accurately mirrors production shape and permissions.
Validate preview, approval, output evidence, and recovery posture before widening workflow scope.
Move to production only after the first evaluator can demo the path without founder narration.
Connector coverage is intentionally narrow during the first rollout.
The first evaluator should use a low-risk environment that accurately mimics production permissions and record shape.
ActionPlane is still in beta posture and does not yet provide formal SLA commitments.