Integration Setup

Connecting Spiro to Paminga is a three-step process: create an authorization in Spiro, connect in Paminga, and choose what syncs. You'll need Spiro admin access for the first step.

Step 1: Create the Authorization in Spiro

1. In Spiro, go to Settings → Integrations and click Configure on the Spiro API card.
2. Click New Authorization.
3. Give the app a name (something like "Paminga"), set the scope to read_write, and set the Callback URL to the Redirect URI shown in Paminga's connect dialog. Copy it from the dialog rather than typing it; it must match exactly.
4. Save, then copy the Client ID and Secret — you'll paste both into Paminga.

note

Spiro stores a single Callback URL per authorization. If you change it later, reconnect from Paminga afterward so a fresh authorization is issued against the new URL.

Step 2: Connect in Paminga

1. In Paminga, go to Settings → Integrations and find the Spiro card (filter by the CRM category if you like).
2. Click Connect. The dialog shows the exact Redirect URI to register in Spiro, plus fields for the Client ID and Secret.
3. Paste the Client ID and Secret and continue. You'll be sent to Spiro to approve the authorization, then returned to Paminga.

When the connection succeeds, the Spiro card flips to "Paminga is connected to Spiro" and its button becomes Configure, which takes you straight to your Spiro sync settings.

Step 3: Choose What Syncs

Syncs Enabled is the master switch — nothing moves in either direction while it's off.

Under Objects to Sync, check the objects you want included:

• Accounts (Spiro Companies)
• Contacts
• Opportunities
• Campaigns (Spiro Campaigns sync as Paminga Marketing Campaigns)
• Campaign Members

Opportunities also switch themselves on the first time you open the Opportunity mappings tab or use the Create Spiro Opportunities action — mapping or creating opportunities is a clear signal you want them synced. Users and picklist options don't appear in the list: every sync includes them automatically, because ownership assignment and picklist translation depend on them.

No Leads?

Spiro doesn't have a separate Lead object — everyone is a Contact. That's why you won't see a Leads checkbox here, and why the Spiro action family works entirely in terms of Contacts.

A few settings deserve a moment of thought:

• Default Account Name — when a contact syncs to Spiro without a company (a personal email address, say), Paminga files them under the account with this name. It defaults to Unknown.
• Default Last Name — Spiro requires a last name; this fills the gap when a contact doesn't have one.
• Allow Spiro to Write Empty Fields to Paminga (and the reverse) — off by default, so an empty field on one side never wipes a value on the other. Turn these on only if you want blanks to win.
• Sync Only The Lead Score On A Lead Score Change — limits score-change-triggered syncs to just the score field.

Run Your First Sync

Go to CRM Sync Status and click Run a Full Sync. You'll see each object type progress in real time — users, picklist options, accounts, contacts, opportunities, campaigns, and campaign members — with counts for pending, completed, and failed items.

Full syncs are safe to re-run anytime. Records are matched (contacts by email, companies by name), not duplicated.

Once your first full sync completes, you're done with manual syncing unless you want it: Paminga checks Spiro for changes about once an hour and pulls in only what's new or updated.

The CRM Sync History page keeps a record of every sync that's run.

After You're Connected

• Head to Field Mappings to control exactly which fields sync, in which direction.
• Set up Actions to push contacts, opportunities, activities, reminders, and campaign memberships into Spiro from your forms, workflows, and imports.