Short Description The general process for connecting Hive9 to an external system — CRM, marketing automation, data warehouse, finance platform. This article covers the high-level flow that applies to most integrations.
What this article answers
- The five-step add-integration process.
- The Push vs Pull distinction.
- What field mapping involves.
Where to start
Go to Settings → Integrations. Click Add Integration (top-right) to start the flow.
The five steps
Step 1 — Choose the platform
Pick from the available integration types:
- Salesforce
- Eloqua
- Marketo
- HubSpot
- Workato
- Data warehouse / EDW
- Other platforms supported in your instance
The platform you pick determines which fields appear next.
Step 2 — Enter credentials
Each platform requires its own authentication info:
- API key / token — for most cloud platforms.
- Username / password — for some legacy integrations.
- OAuth flow — Hive9 may redirect you to the source platform to authorize.
- Connection URL / endpoint — for self-hosted or custom destinations.
Follow the in-form instructions for the specific platform.
Step 3 — Test credentials
Click Test Integration Credentials before saving. Hive9 attempts to reach the source platform with the credentials you entered. You should see a success message.
If the test fails:
- Verify the credentials.
- Confirm the source platform isn't blocking the connection (firewall, IP allowlist).
- Confirm the API user has the right permissions in the source system.
- Contact Support if you can't resolve the failure.
Step 4 — Save
Save the integration. The connection is now established. The integration appears in the Settings → Integrations list with its status.
Step 5 — Configure Push and Pull
The integration has two halves:
- Push — Hive9 sends data to the external system (tactics, line items, costs).
- Pull — Hive9 receives data from the external system (responses, MQLs, deals).
Expand each section and configure separately:
- Enable Push or Pull (or both).
- Specify which Hive9 objects participate (per tactic type via the Model — see Models & Tactic Library).
- Use the dropdowns to expose source-system fields and map them to Hive9 attributes.
- Map only the fields you need — over-mapping creates noise.
Save.
[SCREENSHOT NEEDED — Push/Pull section with field mapping dropdowns]
Mapping data to attributes
Different integrated systems can supply different data:
- One system might provide Responses and MQLs.
- Another might provide Closed Deals and Pipeline.
- A third might provide Master Data (Business Units, Product Lines).
You can have multiple integrations active simultaneously, each providing different data types.
Tactic-Type level enablement
After you set up an integration at the instance level, you must also enable it per Tactic Type in your Model's Tactic Library. Open the relevant Model, find the Tactic Type, and check the Deploy to Integration option.
See Models & Tactic Library.
Folder configuration (Eloqua and Marketo specific)
If you're pushing tactics directly into Eloqua or Marketo, you'll set up destination folders at the Plan level. Folder rules differ:
-
Eloqua — folders can be hierarchical (e.g.,
North America/Pending). -
Marketo — folders must be in the root Marketing Activities folder (no nesting, e.g.,
2017 New Plan).
See Eloqua — folder rules and Marketo — folder rules.
Common questions
How many integrations can I have at once? There's no hard limit. Each integration is a separate connection. Same-type integrations (e.g., two Salesforce instances) are allowed — but only one Salesforce integration per Model (see Models & Tactic Library).
Will my integration work for tactics created before it was added? Existing tactics can be re-pushed after integration setup if your role permits. Future tactics use the integration automatically.
How long until data starts flowing? Push happens on tactic approval (or per the integration's sync cycle). Pull happens on the integration's sync schedule — could be near-real-time or daily, depending on the source platform.
What about error logs? Integration errors are typically captured in Hive9's logs. Contact Support for log review.
Comments
Please sign in to leave a comment.