Factors.ai adds scheduled weekly CRM sync to Salesforce in beta
Factors.ai released Scheduled CRM Sync in beta, which pushes all accounts in a chosen Factors segment to Salesforce on a recurring weekly schedule regardless of activity. The company says HubSpot support is next.
Factors.ai introduced Scheduled CRM Sync as a beta integration feature. Customers choose a Factors segment and the system runs a full sync of all accounts in that segment to Salesforce every week. The sync runs regardless of whether the accounts have recent activity, which differs from activity-triggered updates. The release note says the feature supports property mapping, so Factors fields can be written to chosen Salesforce fields, and an optional daily account cap. HubSpot is named as the next supported CRM.
The details
- Status: beta.
- Destination: Salesforce; HubSpot support is listed as next.
- Runs a full sync of all accounts in a chosen segment on a recurring weekly schedule.
- Syncs accounts regardless of activity.
- Supports property mapping and an optional daily account cap.
Context
Factors.ai has expanded its CRM footprint through 2026. On July 31 it released Salesforce and HubSpot widgets in beta that show account journey timelines and run research agents inside CRM records. Earlier, it made its MCP server available as a hosted URL (June 9) and shipped a first version of its multi-touch attribution Influence model (June 8). Scheduled CRM Sync adds a batch path for segment data.
Not disclosed
- Timing for HubSpot support.
- Whether the feature is included in all plans or carries added cost.
- Salesforce API usage impact for large segments.
- When the feature will leave beta.
- Vendor
Factors.ai- Category
- Measurement & Attribution
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.




