Spiro CRM Integration Overview

Paminga's native Spiro integration keeps your marketing and sales data in sync — and puts marketing engagement in front of your reps without them ever leaving Spiro.

Connecting is self-service and takes a few minutes. Start with Integration Setup — it walks through creating the OAuth app in Spiro and authorizing Paminga.

What Syncs

From Spiro to Paminga, a sync brings over:

• Companies — synced as Paminga Accounts. Matched by name, so a company that already exists in Paminga is updated rather than duplicated.
• Contacts — matched by email address.
• Opportunities — including pipeline and stage. Paminga provisions your Spiro stages as opportunity stage options automatically, and classifies them as open, won, or lost based on each stage's designation in Spiro.
• Campaigns — Spiro Campaigns sync as Paminga Marketing Campaigns, including their membership.
• Users — so contact and account ownership stays meaningful on both sides.
• Field values — standard fields and any custom fields you've mapped, with picklist values translated between the two systems. You control every field in both directions via Field Mappings.

From Paminga to Spiro, records are created and updated when you say so — through Actions. Create or update contacts, create opportunities, log activities on the rep's timeline, schedule reminders, and add contacts to Spiro Campaigns — triggered by form submissions, workflows, contact imports, and anywhere else Actions fire.

Opportunity Stages

Spiro designates every sales stage as Open, Won, or Lost, and Paminga honors that designation exactly. An opportunity in an open stage sits in your pipeline at that stage's default probability. Move it to a won stage and Paminga closes it at 100% probability; move it to a lost stage and it closes at 0%. Forecast categories follow along, so pipeline reporting reads the way your reps expect.

Close dates are real close dates. Spiro stamps an opportunity's close date the moment it closes, and Paminga records that date as the actual close date — including on your first full sync, so deals won long before you connected keep their true close dates in your reporting.

You don't maintain the stage list by hand. The first time a sync encounters a Spiro stage Paminga hasn't seen, the stage is provisioned automatically with settings matching its Spiro designation. If you later change a stage's designation in Spiro, the next sync updates the stage's settings — and re-derives the opportunities sitting in it — to match. Default probabilities on your open stages are yours to tune in Paminga; syncs leave them alone.

Record Links

Once a contact or account is synced, its detail page in Paminga shows a CRM Relationships panel with a direct link to the matching record in Spiro. One click takes you from a Paminga contact to the same person in Spiro.

How Syncing Runs

• Spiro → Paminga: run a full sync anytime from the Sync Status page — one click, and you can watch each object type progress in real time. After your first full sync, Paminga also picks up Spiro-side changes automatically about once an hour, fetching only records that changed since the last run. Re-running a sync is safe: records are matched, not duplicated.
• Paminga → Spiro: event-driven. The moment an action fires — a form is submitted, a workflow step is reached, an import completes — the corresponding record is written to Spiro.
• Deletes never propagate. Deleting a record on either side does not delete its counterpart. A contact deleted in Spiro does leave the integration's synced contact list on the next sync — the Paminga contact and its history stay intact.