Common integration patterns in Allocadia — Workato, SFTP, SFDC, file-based

Allocadia integrates via Workato recipes, SFTP file drops, the Salesforce Connector, and direct API calls. Pick the right pattern for your source.

Workato recipes

Workato is a popular integration platform used by many Allocadia customers for bidirectional sync. Common recipes:

• Salesforce → Allocadia metadata sync (campaigns, opportunities, custom fields).
• Snowflake or other warehouses → Allocadia for line item or actual data.
• Allocadia → downstream BI tools for reporting-side ingestion.

Workato recipes typically authenticate against Allocadia's REST API using a dedicated integration user.

SFTP file imports

SFTP is the standard pattern for CSV-based imports of POs, Actuals, and bulk Line Item data. Your upstream system drops a CSV at an Allocadia-provided SFTP folder on a schedule; Allocadia picks it up and loads the rows per the configured import template.

Best for recurring, high-volume data from systems that already produce extracts (ERPs, accounting tools).

See Importing POs and Actuals via SFTP into Allocadia for the full flow.

Salesforce Connector

Allocadia maintains a Salesforce Connector for pulling campaign and opportunity data into Allocadia. Used by customers whose Marketing Operations lives in Salesforce.

Some legacy accounts use a per-FY integration user pattern — see Salesforce connector in Allocadia — per-FY user setup pattern.

Direct REST API calls

For custom integrations with internal systems you control, call the REST API directly:

• Create or update Line Items programmatically.
• Pull data for custom reporting dashboards.
• Build approval workflows that trigger external systems.

See The Allocadia REST API — overview of endpoints for scope.

Who sets up the initial configuration

Initial integration setup is typically a Professional Services engagement:

• Import templates, SFTP credentials, and column mappings are configured by PS.
• Salesforce Connector initial setup is PS.
• Workato recipe design (if a new recipe) is PS or your team.

Once configured, your team operates the integration day-to-day; Support handles minor adjustments and troubleshooting.

Related articles

• The Allocadia REST API — overview of endpoints
• Importing POs and Actuals via SFTP into Allocadia
• Salesforce connector in Allocadia — per-FY user setup pattern
• Our Workato integration with Allocadia is failing — common causes