Skip to main content

Logging FirstIgnite emails and activity to Minuet CRM

When you send an email from FirstIgnite, FirstIgnite can record it in Minuet as a remark, filed against the record you choose.

Before you start: a team owner or admin must enable CRM activity logging in FirstIgnite, under Minuet Settings (app.firstignite.com/inteum/settings). Your own FirstIgnite login email also needs to match a contact in Minuet, or you'll be asked to pick an author before anything will be logged.

What FirstIgnite proposes

Before you send, the Log to panel shows where the activity will go and who FirstIgnite will attribute it to.

The record. FirstIgnite starts from the contact you're emailing. If the FirstIgnite project is linked to a Minuet technology and that contact has a live Marketing Target for it, the activity goes on the target. FirstIgnite prefers one on the technology itself, otherwise one on a Marketing Project linked to it. With nothing more specific to go on, it files against the contact.

The author. FirstIgnite looks up the sender's own email address in Minuet. A matching contact becomes the author.

Change either. To leave this message out of Minuet entirely, tick Don't log this email.

The Log to Minuet panel before sending, proposing a Marketing Target as the record and the sender as the author, each with a Change link

The Log to Minuet panel before sending, proposing a Marketing Target as the record and the sender as the author, each with a Change link

Why there's no default technology

Offices genuinely differ. Some log outreach under the technology, some under the contact, some under the marketing target. A technology can have several marketing projects too, so FirstIgnite can't infer the right project from the technology either. Any global default would be wrong for someone, so FirstIgnite proposes what it can work out and leaves the rest to you.

Creating a target from a project's marketing panel does pick the right record automatically, because there the context is unambiguous.

Choosing a different record

The Log to dropdown offers seven record types:

  • Marketing Target

  • Contact

  • Company

  • Technology

  • Marketing Project

  • Agreement

  • Patent

Pick a type, search for the record, and select it. The panel also suggests recent targets under Suggested targets.

The Log to dropdown open, listing the seven record types

The Log to dropdown open, listing the seven record types

What will stop it being logged

The person has to be linked. FirstIgnite won't file an activity against a guess. If the recipient isn't linked to a Minuet contact, the panel says "This email won't be logged — link the contact to Minuet first." and offers Link to Minuet. See Matching and adding contacts and companies in Minuet CRM.

The Log to Minuet panel for a recipient who isn't linked yet: This email won't be logged, link the contact to Minuet first, with a Link to Minuet button

The Log to Minuet panel for a recipient who isn't linked yet: This email won't be logged, link the contact to Minuet first, with a Link to Minuet button

The author has to be resolved. If FirstIgnite can't match the sender to a Minuet contact you'll see "We couldn't match you to a Minuet contact — choose an author to log this email". Pick one. There is no fallback, and Minuet rejects a remark with no author, so leaving it blank means the email sends and isn't logged. The panel tells you as much before you send. This is the usual answer to "why wasn't my email logged?"

Neither stops the email. The message sends either way. FirstIgnite writes the remark shortly after it goes out, not during the send.

Who the remark is attributed to

The person who sent it. The API credential your Minuet administrator set up is transport only. It never appears as the author of a remark.

Recipients

On Minuet 20.0203 and newer, recipients who are linked Minuet contacts get their own rows on the remark's Recipients tab. Anyone not in Minuet appears in the body of the remark, marked as such, so nobody is dropped.

On older builds Minuet doesn't accept recipient rows through the API, so every recipient goes into the body. Nothing is lost. It just isn't structured. FirstIgnite decides this from your Minuet version, and if it can't read the version it uses the body.

There is one side effect. If the sender's or the main recipient's address isn't already on their Minuet contact record, FirstIgnite adds it as an additional, non-primary address so the activity attributes correctly. It never creates a contact, and it never adds addresses for other recipients.

Up to 50 recipients per message.

What gets written

The email's HTML body, the recipients, the author, and the record it's filed against. FirstIgnite files it as an outbound remark. There is nothing to configure.

Seeing it afterwards

Logged activity appears in the Minuet Marketing tab on the contact, and in Minuet.

FirstIgnite files the remark against the record you chose. How Minuet then relates that record to others is Minuet's own behaviour. If you need the activity visible at a particular level, file it there.

Minuet itself keeps remarks marked private in Minuet out of reports, so they never appear in FirstIgnite, including ones your own team wrote.

What this doesn't do

  • No attachments on email sent from FirstIgnite.

  • One recipient per message. There's no bulk send.

  • Replies aren't threaded back into the original Minuet remark.

  • No bounce or undeliverable notifications come back into Minuet.

  • Nothing syncs the other way. Campaign status and outcomes don't write back onto a Marketing Target.

If something isn't working, see Troubleshooting the Minuet integration.

Did this answer your question?