Qordo
Qordo is an Activation destination for MySQL/AnalyticDB tables and views. It requires a workspace configured for native execution and admitted MySQL and Qordo connector versions. If setup returns not_ready, ask your administrator to complete that setup.
In Activation → Qordo, select an existing native warehouse or choose Connect a new MySQL / AnalyticDB warehouse. Enter a TLS-enabled host, database, username, and password. Daspire stores the username and password as an encrypted workspace credential and keeps only its opaque handle in source configuration. The database account needs read access only to the tables or views used by the Activation. Daspire does not create a temporary Airbyte source.
After the connection check, select a discovered table or view and its non-empty, unique business key. Setup preview reads at most ten rows for inspection. The final change preview performs a complete bounded read; a partial or failed read cannot become a runnable change list. Put filtering and calculations in a database view.
Create a Qordo API token with access to the intended workspace, List, members and task fields. Enter it in the Qordo Activation connection form. Daspire encrypts the token and returns a credential handle. The token does not appear in Activation configuration or run results.
Select the workspace and browse its spaces, folders and Lists before mapping fields. Field discovery depends on the Qordo deployment version; unavailable inherited custom-field discovery prevents using those custom fields. Basic task fields can still be configured when their required APIs are available.
Supported task fields are title, description, priority (low, medium, high, critical), due date with an explicit timezone, status UUID and one assignee. Custom fields support the validated text, number, date, checkbox, URL, dropdown and multi-select definitions returned by Qordo. Unknown definitions, deleted fields and invalid option values are rejected.
Numeric mappings accept non-negative numbers and decimal numeric strings. Due dates need an explicit timezone; use a warehouse view to format a SQL date/time that has no timezone.
For rotation, pause affected activations, create/check a new handle, rediscover the List, update the destination to the new handle and recompile before enabling it. Handles are immutable; rotation does not alter in-flight requests. Uncertain requests that cross token revisions may require reconciliation.
Start with a manual run. Run details report created, updated, skipped, failed, and reconciliation-required rows separately. Retry unfinished records resumes the original immutable operations and does not reread corrected warehouse values. Start a new manual run after correcting source data. Removing a source record keeps its Qordo task; if it returns, Daspire resumes the existing task binding.
The shared request budget starts at 45 requests/minute per Qordo identity, including discovery and writes. Qordo's documented API limit is 60/minute per token. Rows with custom fields may need more than one request. Large runs can therefore take several minutes.