For admins
Open field mappings
Go to Settings → Connections → Integrations → CRM and open the Field mappings tab. You need the Integration manage permission to make changes. The cards across the top show each mapped object, how many mappings it has, and which Alguna record it’s written from. A green dot means the object is enabled and has mappings. If more than one CRM is connected, choose a Default CRM on the Settings tab first. Alguna maps fields onto that CRM.Map fields onto deals
Every CRM connection comes with a deal object: Deal in HubSpot, Opportunity in Salesforce. Alguna fills it from the deal’s primary quote. See how quotes and deals are linked.1
Select the deal object
Click the Deal or Opportunity card.
2
Add a mapping
Click Add mapping. On the left, select the Alguna field, such as ARR or Contract start date. On the right, select the CRM field it should fill.
3
Save
Add as many mappings as you need, then click Save field mappings. Changes apply once you save.
Map another object
You can also write Alguna data onto other CRM objects:- HubSpot: companies, contacts, tickets, quotes, line items, products, and custom objects
- Salesforce: any standard or custom object the connected Salesforce user can read, create, and update, such as Account or Contract
1
Add the object
Click Map an object. Choose the Alguna record the data comes from and the CRM object it should be written to.
2
Set a parent for child records
Phase item, phase item tier and credit records sit under a parent. Choose the Parent mapped object, then name the link between them. In HubSpot, that’s an association label. If no association with that name exists yet, Alguna creates it in HubSpot when you save. In Salesforce, choose the lookup field on the child object that points to the parent object.
3
Add field mappings
Click Add, then map fields as you would for deals.
A phase is a period of a subscription with its own pricing, and a phase item is one product in that phase. To send subscription products to HubSpot line items, map a Phase item record onto line_items, with your subscription object as its parent. In Salesforce, map it onto a custom object for subscription lines that has a lookup field to your subscription object.
Alguna creates these records the first time it writes them and updates the same records after that. When a product, tier or credit is removed from a subscription, Alguna deletes its record from the CRM. Subscriptions that are still being negotiated, such as drafts or sent quotes, aren’t written until they’re active.
In HubSpot, Alguna needs read access to your custom object schemas to list custom objects. If you connected HubSpot before this was available and only see standard objects, reconnect HubSpot. In Salesforce, formula and other calculated fields aren’t offered, because they can’t be written.
Salesforce: moving from the Alguna custom fields
The Alguna custom fields on the Salesforce Account are written by the subscription sync in External sync. Field mapping replaces it with records and fields you choose. You can’t enable a Subscription mapped object on an integration while that subscription sync is still set up, so remove the subscription configuration from External sync first, then map the values you need. Contactsupport@alguna.io if you’d like help moving over.
Use a formula
Click fx on a mapping row to write a calculated value instead of a single field. Click it again to go back to a single field.
Formulas can use
mrr, arr, acv, and one_off_total, the operators + - * / %, and parentheses. Pass product IDs to product_arr() and product_mrr(). With no arguments, they cover the whole deal. tier() and overage_tier() accept rate, min_units, max_units, fixed_fee, and percentage.
Worth knowing:
- A product the deal doesn’t sell counts as zero instead of causing an error, so an out-of-date product ID quietly lowers the result
product_arr()can be less thanarr, because contract-level adjustments such as minimum spend, ramps, and contract discounts don’t belong to any single productone_off_totalis the deal’s one-time charges with their discounts applied. The recurring figures leave these out, and TCV is ARR over the contract term plus the one-time total, so no line is counted twice- Tier positions start at 1. If you ask for a tier that doesn’t exist, the field is left empty instead of being set to zero.
Match field types
Map each Alguna field onto a CRM field of a compatible type:
Alguna only lists CRM fields it can write to. Each CRM field can be mapped only once.
When values are written
Deals and opportunities are written:- Whenever the primary quote changes
- When the quote’s subscription changes, while the quote is a draft, pending approval, or sent
- When the quote is signed
Write automatically
When Write automatically is on, Alguna writes the object whenever its source changes. When it’s off, Alguna only writes the object when you click Sync now on a quote’s deal card or when an automation does it. Objects under a parent follow the parent’s setting.Empty values
When there’s no value to send, for example because a deal has no primary quote, Alguna clears the CRM field so it never shows an out-of-date number. Yes/no fields are set to no instead of being cleared. Dates are written asYYYY-MM-DD.
Required fields
If a CRM object requires fields to be filled in when a record is created, Alguna shows a warning listing them. You can still save, because a workflow in your CRM, such as a HubSpot workflow or a Salesforce flow, might fill them in. If nothing does, new records will fail to sync, so map each required field or choose one as the parent link.Turn off, remove, or delete
- The Enabled switch turns an object on or off without losing its mappings. Each mapping row also has its own active switch.
- Removing a mapping stops Alguna updating that field. It doesn’t clear the value already in your CRM.
- Delete object removes the object, its mappings, and every object under it. This can’t be undone.
Send credits to your CRM
For a step-by-step setup, see the Credits in your CRM walkthrough. Credits on a subscription can reach your CRM in three places. Use whichever fits how your team reads them:Credits on line items
A line item shows only the credits scoped to its own product or price, in its own phase. A credit for one product doesn’t appear on the other products’ lines. A credit that applies to all products isn’t tied to any one line, so it appears on the subscription and Credit records rather than on every line. When exactly one credit is scoped to a line, the line also gets that credit’s own fields, such as its name, amount, duration and dates. When several are, those fields stay empty and the credits summary lists each one. Map a Credit object to get a record per credit. For example, a subscription with a one-time credit of 10,000 units scoped to one product writes this onto that product’s line: Credit count1, Unit credit total 10000, Credit type units, Credit duration type once, and the credit’s start date. The subscription’s other lines get a Credit count of 0.
Duration and dates
Credit duration works like a discount’s duration:
Credit start date is when grants begin: the date the phase’s credits were activated, or the phase start date until then.
Other credit fields
- Credit product IDs, Credit product names and Credit product SKUs list the products the credit is scoped to, separated by semicolons. They’re empty for a credit that applies to all products. Use them to match a Credit record to its line item.
- Credit monetary amount and Credit currency are set only for monetary credits. Map Credit amount to cover units credits too.
- Totals and the credits summary on a subscription or quote read the same phase as revenue. Each grant counts once, however often it recurs.
Fields you can map
The fields on offer depend on the object’s Alguna record.
Some values are only available in certain cases:
- Quote, revenue, and subscription values need the CRM record to have a linked quote. A record written from a signed quote always has one.
- Opportunity values need the subscription’s primary quote to be linked to a CRM deal or opportunity
- Tier and overage values only exist for tiered prices
- Credit values depend on where the credit applies. See Send credits to your CRM.
Troubleshooting
For sales reps
Some fields on your deals and opportunities, such as MRR, ARR, TCV, contract dates, and signer, may be filled in by Alguna. They always reflect the deal’s primary quote.- Don’t edit these fields in your CRM. Your change will be replaced the next time the value changes in Alguna.
- If a number looks wrong, check which quote is the deal’s primary quote. In HubSpot, it’s marked Primary on this deal in the Alguna - Deal Quotes card. In Salesforce, check the quotes linked to the opportunity in Alguna.
- To change a value, update the quote in Alguna