ServiceNow Ticketing
ServiceNow Ticketing can be evaluated in a vendor-provided developer environment before you connect a customer-owned sandbox.
Sandbox availability
Keep the first connector setup constrained to one environment, one identity, and one clearly reviewable workflow.
Create a ServiceNow Personal Developer Instance
Use the official developer signup to provision a Personal Developer Instance so the first incident workflow runs in a safe non-production environment.
Create a least-privilege integration user
Create a dedicated ServiceNow user with access only to the incident workflow fields needed for state, close_notes, close_code, and work_notes.
Collect the instance URL and workflow allowlist
Record the ServiceNow instance URL, service username, password, and the narrow incident field allowlist you want to govern first.
Enter the ServiceNow settings in ActionPlane
Open the ServiceNow connector page in ActionPlane, save the instance credentials, validate auth, and sync metadata so the incident dictionary is visible before you run anything.
Run one incident sample as a dry run
Use the canonical incident sample first, confirm the preview and approval story, then allow one live incident closure only after the dry run looks correct.
Business context
Support Ops wants AI to close a duplicate alert after the operator confirms the incident should be resolved.
Starting record state
Incident `INC-42` is open, customer impact is low, and the close code plus notes are still empty.
Requested change
Set the incident to closed, attach the reviewed resolution summary, and record the close code plus work note.
Why it routes
A visible state transition plus customer-impact evidence makes this a strong first ticketing workflow for simulation or a developer instance.
Expected artifacts
Preview, approval or execution evidence, incident-close metadata, and audit events all stay on the same run.
Reset behavior
Reset clears the sample incident history back to the initial open-ticket story.
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.
{
"instanceUrl": "https://contoso.service-now.com",
"clientId": "\u003Cservice-username\u003E",
"clientSecret": "\u003Cservice-password\u003E",
"isSandbox": true,
"isEnabled": true,
"validateAfterSave": true,
"syncMetadataAfterSave": true,
"managedObjects": [
{
"objectApiName": "incident",
"displayName": "Incident",
"allowedFields": [
"state",
"close_notes",
"close_code",
"work_notes"
]
}
]
}
curl -X POST \ "$ACTIONPLANE_BASE_URL/api/connectors/onboarding/servicenow-ticketing/connect" \ -H "Authorization: Bearer <session-token>" \ -H "Content-Type: application/json" \ --data @"connect-servicenow-ticketing.json"
Re-run auth and instance validation without resubmitting the connector payload.
curl -X POST \ "$ACTIONPLANE_BASE_URL/api/connectors/onboarding/servicenow-ticketing/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/servicenow-ticketing/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.
ActionPlane documents the sandbox lane clearly, but the fully seeded simulation workspace is not available for this connector yet.
Keep the first workflow narrow so validation and metadata freshness remain obvious during evaluation.
Use only non-production records while the connector remains in beta posture.