Texada setup guide
Review credentials, connection steps and the first sync-rule workflow.
Connect two platforms, map your fields once, and let synkazo keep them in sync.
Connect Texada, verify credentials, review field mappings, and configure your first synkazo sync rule.
Set up the Texada source connection, verify it, and configure your first synkazo sync rule.
Install synkazo for HubSpot first, then choose Texada as the source platform for your project. The source platform and project sync mode are permanent choices for that project.
Open the project Connections tab, and choose Texada as the source if the project still asks you to pick one.
Select Connect on the Texada card, then Manual Setup.
Enter the Tenant and API Key.
Select Verify Credentials and continue only once synkazo confirms the connection.
When you create a sync rule, synkazo loads the objects and fields available to the connected account. Current connector coverage includes:
The object selector in synkazo is authoritative for your account; availability can depend on connector access and your synkazo plan.
From the Connections tab, select Next step: Create Sync Rule.
Choose a Texada source object and the HubSpot destination object.
Confirm the rule behavior, review the proposed field mapping, and choose one mapping as the match field.
Choose a schedule for the rule.
Create the rule, set it to Active, select Start Sync, then Sync All to establish the first complete baseline.
Open Run History to confirm the run completed and review created, updated, skipped or failed records.
Check every value is copied without trailing spaces, and that the API application is active in the source platform. For ServiceTitan, the App Key, Client ID, Client Secret and Tenant ID must come from the same API application.
Open the activity log for that sync rule. Each skipped or failed record is listed with the reason — most often a required HubSpot property is missing from the mapping.
This means no match field was set, or the match field is empty on some records. Set a match field with a reliably-populated value, such as email or an ID field.
The app was uninstalled in HubSpot or its permissions changed. Click Reconnect in the dashboard — nothing is lost, and mappings are preserved.
Field types must be compatible. If synkazo flags a mismatch it will propose a conversion — accept it, or map to a different property with a matching type.
Continue evaluating
Review credentials, connection steps and the first sync-rule workflow.
Compare a maintained connector with Zapier-style workflows and other approaches.
See the documented problem, mapping approach and intended operational outcome.
Compare plan limits and prepare the questions needed for an accurate scope.