Getting Started

Welcome to the team. Here's how the Crate & Co. Integration project is set up and what to do first.

The players

• Mithra Systems - that's us. We sell goods; we don't ship them.
• Crate & Co. - our logistics partner. Their platform exposes an order API. You'll talk to it a lot; Cyrus Bahrami on their side owns the spec.

What is an integration?

An integration is two systems exchanging data over the network. Think of it like a conversation. There is a request and a reply. The common language the two systems speak is defined by the API.

From your Salesforce org's perspective, integrations can either be:

• Outbound - your Salesforce org starts the conversation, reaching out to another system to send or get some data.
• Inbound - another system starts the conversation, reaching into your org.

How the work is organized

Everything lives on the CCI board as two issue types:

• Spikes - short research tickets. Read the linked material, then hit Resolve. No org changes required.
• Tasks - hands-on tickets. You build something in your org, then Submit for QA. The QA team will run checks against your org and either pass the ticket or send it back with feedback. This is how we make sure you build things according to the architecture spec.

Your first day

1. Make sure you have a Salesforce org you can build in.
2. Work the board top-down - the tickets are ordered so each one builds on the last.
3. When a ticket references the API, keep the API Reference open in another tab.

Head to the board and pick up CCI-1 if you haven't already.

Tools

• You're welcome to use either Flow or Apex
• VS Code, Cursor, etc - your local IDE doesn't matter for us, just make sure your solution is deployed to the same org you've connected Camp Apex with