Meraki - Current Org Target
Overview
When you access Cisco Workflows for the first time, a Cisco-managed Meraki target is automatically created for your organization. This target serves as the default connection endpoint for all Meraki-related workflows and does not require any manual setup.
How It Works
Automatic Creation
The Meraki target is automatically provisioned for your organization based on your Dashboard user permissions when any of the following occurs:
-
You access Automation in the Meraki Dashboard for the first time.
-
A new tenant is created with the Meraki flag enabled.
-
The system runs its scheduled sync (every 24 hours) and detects a tenant without a Meraki target.
Automatic Updates
The Meraki target is kept in sync with Meraki module metadata. If there are changes to the metadata, the target is automatically updated during the next scheduled sync — no action is required from you.
Authentication & Tokens
Token Provisioning
When you access Automation for the first time, two refresh tokens are automatically created:
| Token | Purpose |
| User token | Used for on-demand workflow execution |
| Org-scoped token | Used for scheduled workflow execution |
-
Make sure you don’t remove User token as it impacts executing workflows.
-
Make sure you don’t remove Org-scoped token as it impacts executing scheduled workflows.
Per-User Isolation
Each user gets their own access and refresh tokens. Your tokens are isolated from other users in the organization — the system uses your specific token when you run a workflow.
Automatic Token Refresh
On subsequent visits, the system checks your token validity. If your token has expired or is no longer valid, it is refreshed automatically.
Workflow Execution
| Execution Type | Token Used | Who Can Run |
| On-demand workflows | User-specific access token | Any user with appropriate permissions |
| Scheduled workflows | Org-scoped token | tenant_admin role only |