Migrating n8n workflows to Ascerta
Migrating existing workflows
The current Ascerta n8n package is @ascerta/n8n-nodes-ascerta. Its workflow node types begin with @ascerta/n8n-nodes-ascerta. and its credential types include ascertaApi and ascertaDatabricksApi. The package includes chat-model nodes for OpenAI, Anthropic, Azure AI Foundry, Amazon Bedrock, and Databricks, plus the standalone Ascerta Proxy node.
Legacy migration toolkit compatibility
The n8n migration toolkit was written for the old n8n-nodes-payi package. Its migrate-workflows-to-payi.py replace strategy creates the old n8n-nodes-payi.* node types and payiApi credentials. Those workflow copies will not use the new Ascerta package. Do not run --strategy replace or --strategy both against a deployment using only @ascerta/n8n-nodes-ascerta until the toolkit is updated for the new IDs.
The toolkit's existing script filenames and PAYI_BASE_URL / PAYI_API_KEY environment variable names have not been renamed. Consult its repository documentation before using its credential-only redirect or audit features. Redirect changes existing provider credentials rather than replacing workflow nodes; test them in a non-production n8n instance first.
Manual migration to the current package
- Export or back up the workflows and credentials you plan to change.
- Install
@ascerta/n8n-nodes-ascertaand restart n8n. - Create an Ascerta API credential with your Ascerta API key and Base URL. For Databricks, also create an Ascerta Databricks API credential with your workspace URL and personal access token.
- In a copy of each workflow, add the corresponding Ascerta chat-model node to the AI Agent, select its Ascerta and provider credentials, and configure the model or deployment. For regular workflows, use the standalone Ascerta Proxy node instead.
- Run the copied workflow and confirm the request and use case appear in Ascerta before deactivating the original.
See Configuring n8n Workflows for Ascerta for current node type IDs and provider-specific settings. Keep the original workflows until the migrated copies are validated; you can roll back by reactivating them.
Updated 1 day ago