sales-jitterbit

What this skill does

# Jitterbit Platform Help

## Step 1 — Gather context

If `references/learnings.md` exists, read it first for accumulated platform knowledge.

Ask the user:

1. **What do you need help with?**
   - A) Integration development — connectors, data mapping, process building
   - B) API Manager — design, publish, secure, monitor APIs
   - C) App Builder — low-code app/workflow building
   - D) EDI / B2B — trading partner setup, X12, EDIFACT
   - E) Agent Management / AI — agents, MCP, AI integration
   - F) Deployment — agent groups (cloud, private, hybrid), runtime config
   - G) Monitoring / troubleshooting — logs, Session Trace, Operation Log errors
   - H) Pricing / licensing — per-connection costs, bundle optimization
   - I) Migration — Design Studio to Integration Studio, or from competitor
   - J) Something else — describe it

2. **Which Jitterbit product are you using?**
   - A) Integration Studio (web-based, current recommended)
   - B) Design Studio (desktop, legacy but still widely deployed)
   - C) API Manager
   - D) App Builder
   - E) Not sure / evaluating

3. **What's your deployment model?**
   - A) Cloud agents (Jitterbit-managed)
   - B) Private agents (on-premises / behind firewall)
   - C) Hybrid (cloud API gateway + private agents)
   - D) Not sure / evaluating

**Skip-ahead rule**: if the user's prompt already provides enough context, skip to Step 2. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask 1-2 critical clarifying questions.

## Step 2 — Route or answer directly

| Problem domain | Route to |
|---|---|
| Connecting Jitterbit to Salesforce/HubSpot/CRM | `/sales-integration {question}` |
| CRM comparison — Salesforce vs HubSpot vs others | `/sales-crm-selection {question}` |
| Salesforce-specific config (Flows, Apex, SOQL) | `/sales-salesforce {question}` |
| Simple no-code Zapier/Make automations | `/sales-integration {question}` |
| Boomi-specific questions | `/sales-boomi {question}` |
| Workato-specific questions | `/sales-workato {question}` |
| MuleSoft-specific questions | `/sales-mulesoft {question}` |
| Celigo-specific questions | `/sales-celigo {question}` |
| SnapLogic-specific questions | `/sales-snaplogic {question}` |
| CRM data quality / deduplication | `/sales-data-hygiene {question}` |
| Integration architecture strategy | Answer directly — read platform guide |
| Connector setup or troubleshooting | Answer directly — read platform guide |
| API Manager / gateway / security profiles | Answer directly — read platform guide |
| Pricing optimization | Answer directly — read platform guide |

When routing, provide the exact command.

## Step 3 — Jitterbit platform reference

**Read `references/platform-guide.md`** for the full platform reference — Harmony architecture, products (Integration Studio, Design Studio, API Manager, App Builder), connectors, pricing, agent groups.

Answer the user's question using only the relevant section. Don't dump the full reference.

If the question involves the Harmony Management API, also **read `references/jitterbit-api-reference.md`** for endpoints, authentication, and regional base URLs.

## Step 4 — Actionable guidance

You no longer need the platform guide — focus on the user's specific situation.

**Connector selection shortcut**: Check the Connector Marketplace first. If no pre-built connector exists, use the HTTP or REST connector for any API, or build a custom connector with the Connector SDK (Java). Technology connectors (Database, File Share, HTTP, FTP/SFTP, LDAP) are always available.

**Deployment decision shortcut**: Cloud agents for fastest start and no infrastructure. Private agents for on-prem data that can't leave the network. Hybrid (cloud API gateway + private agents) for the most common enterprise pattern — gives you cloud management with behind-firewall execution. All agent traffic is outbound-only HTTPS, so no inbound ports needed.

**Cost optimization shortcut**: Jitterbit uses tier-based connection pricing (Standard 2-3 connections, Professional 5, Enterprise 8+). Each additional connection negotiation can be expensive — audit your active connections and consolidate where possible. Premium connectors (SAP, Workday) carry separate fees. Multi-year contracts typically save 10-25%.

**Studio choice shortcut**: Integration Studio (web) is where Jitterbit is investing — use it for new projects. Design Studio (desktop) is legacy but still fully supported — only stay on it if you have complex existing projects that haven't been migrated. There is no automatic migration path; plan for a rewrite.

If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.

## Gotchas

> *Best-effort from research — review these, especially pricing details and feature availability which change frequently.*

- **Per-connection pricing is unpredictable.** Teams that start with 3-5 connections often find themselves negotiating expensive tier upgrades within 12 months. Map your connection count before signing, including "invisible" connections like local disk and HTTP. Premium connectors (SAP, Workday) are a separate line item beyond the base subscription.
- **Individual record errors pass silently.** A Jitterbit operation can report "Success" while individual Salesforce record updates fail. There's no built-in alert when a data update fails — you have to build error routing in Jitterbit or create audit reports in Salesforce to catch them. Always add error-trapping scripts after every bulk upsert.
- **Logging is limited.** Operation logs lack rich text formatting and alternative logging formats, making it hard to review and analyze processes after runtime. Enable Debug Logging only while troubleshooting — it generates a lot of data — and combine with Session Trace for deeper inspection.
- **No native source control.** Jitterbit has no code branching or Git integration built into the platform (as of 2026). If IT leadership requires source control, you have to export projects and manage versioning externally. This is the single most cited blocker for Jitterbit adoption in mature IT organizations.
- **CDC support is limited.** Change Data Capture connectors are the most-cited technical gap in user reviews. If you need real-time data replication for analytics, plan to supplement with a dedicated CDC tool (Debezium, Fivetran) or use polling + timestamps.
- **Authentication tokens expire quickly.** Harmony Management API tokens are documented to expire after 15 minutes (observed up to 5 hours in practice). For unattended API access, build refresh logic or use service accounts. TFA configured as "on each login" breaks unattended API access — disable TFA for service accounts or use bypass rules.
- **Integration Studio and Design Studio are not interchangeable.** Projects built in one cannot be opened in the other. If you're starting new work, use Integration Studio. If you inherit a Design Studio project, plan for a rewrite when you're ready to modernize — there is no automatic migration.
- **Design Studio debugging is harder than Integration Studio.** Design Studio has less visibility into runtime behavior. If you're troubleshooting a hard bug and your project is in Design Studio, sometimes the fastest path is porting the problematic operation to Integration Studio temporarily for debugging.

- **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date.

## Related skills

- `/sales-boomi` — Boomi platform help — enterprise iPaaS, 1000+ connectors, API Management, Data Hub MDM (direct competitor)
- `/sales-workato` — Workato platform help — enterprise iPaaS, 1200+ connectors, recipe automation, MCP Gateway (direct competitor)
- `/sales-celigo` — Celigo platform help — mid-market iPaaS, 1000+ connectors, AI error management, NetSuite depth (direct competitor)
- `/sales-snaplogic` — SnapLogic platform help — enterprise iPaaS, 1000+ Snaps, Agent