Field Mappings
Field Mappings is where you control the flow of data field-by-field. Each row pairs a Spiro field with a Paminga field — standard rows come pre-paired, custom rows wait for you to pick — and gives you two checkboxes: Sync from Spiro (download) and Sync to Spiro (upload). Checked means that direction syncs; unchecked means it doesn't. It's that direct.
There are three tabs — Account, Contact, and Opportunity — the object types with mappable fields. (Campaigns, campaign members, and users sync too — they just don't have fields to map.)
Standard Fields
Paminga ships each tab with sensible standard pairings already in place: name, email, phone, address fields, title, website, and so on. On the Account and Contact tabs they sync in both directions out of the box, and you can toggle either direction off per field. Opportunity standard fields are the exception — they sync from Spiro only.
A few rows behave differently, on purpose:
- Contact Email and Account Name are the match keys — they're how Paminga recognizes the same record on both sides — so they always sync and can't be unmapped.
- Spiro's system fields (record ids, created/updated timestamps, last activity date, owner ids) are shown but locked. Paminga won't write into Spiro's bookkeeping, and these locks are enforced server-side, not just in the UI.
Custom Fields
Every mappable custom field in your Spiro org appears automatically, straight from Spiro's live metadata. To map one, pick a Paminga field from its dropdown — the list is filtered to type-compatible fields only, so you can't map a picklist to a number field by accident.
Don't have a matching Paminga field yet? Click the + next to the row to create one on the spot, without leaving the page.
Mappings save as you set them. Unmapped fields never sync.
How Spiro Field Types Map
| Spiro type | Paminga type |
|---|---|
| Short Text / Long Text | Text |
| Single Picklist | Dropdown |
| Multi Picklist | Multi-Select |
| Number | Number / Decimal |
| Currency | Decimal |
| Date | Date |
| User Picker (Contacts) | User lookup |
Picklist values are translated by label in both directions — a contact whose Spiro Contact Type is "Vendor Contact" arrives in Paminga with the matching dropdown option selected, and vice versa. Multi Picklist values translate the same way, option by option.
Spiro field types with no marketing-automation equivalent — Link, Attachment, and the record-picker types (Company Picker, Contact Picker, and the like) — are excluded from the mapping page rather than synced as raw internal ids. The one exception is Spiro's User Picker on Contacts, which maps to a Paminga User lookup with the user reference translated properly.
The Opportunity Tab
Opportunity standard fields sync from Spiro to Paminga only. Spiro derives fields like stage, pipeline, and amount from the opportunity itself, so Paminga doesn't write into them after creation — opportunities are created from Paminga via the Create Spiro Opportunities action, which sets them at creation time.
Custom opportunity fields are the exception: map one with Sync to Spiro enabled and the Create Spiro Opportunities action can populate it on the opportunities it creates. The mapping authorizes the write — the value itself comes from the field/value pairs you set in the action's config.
