Captured.
Joachim, VP Marketing at an account in your market, comments on a competitor’s LinkedIn post.
Postelix sends the people who engage with you or your competitors on LinkedIn to HubSpot as contacts, with 17 Postelix fields and a note on the timeline. It reads your lists, owners, deals and sales activity back, so customers and people with an open deal stay out. Included in the one plan, EUR 1,490 a month per market.
To HubSpotFrom HubSpotBoth. Postelix writes contacts, its own fields, a list and notes. It reads your lists, owners, lifecycle stages, open deals, companies and activity back.
Postelix’s own record link first, then the email, then the LinkedIn URL. If two contacts share the LinkedIn URL, nothing is written.
New interest goes out every 30 minutes. HubSpot is read back every hour.
Included in the one plan, EUR 1,490 a month per market. Nothing is charged per record.
Sixteen HubSpot permissions, approved by a HubSpot user with Super Admin or App Marketplace access.
The core Postelix platform runs on EU-hosted infrastructure. For AI processing you choose an EU or a US route.
Slack alerts, CSV and the API are on the integrations overview.
One person, step by step, with automatic sending switched on. An illustration with made-up names, not a screenshot.
Joachim, VP Marketing at an account in your market, comments on a competitor’s LinkedIn post.
Postelix looks for him by its own record link, then his email, then his LinkedIn URL. No contact matches, so he is new.
A new contact with his name, title, company and email, plus the Postelix fields. He joins the static list “Postelix: LinkedIn interest”.
One note on his timeline for this signal: what he did, whether his email is verified, and a link to his record in Postelix.
Your own HubSpot workflows act on him, for example on the list or on the field Postelix sent by.
Every hour Postelix reads HubSpot again and shows his owner and open deals on his card. Once he is a customer or has an open deal, he is not sent again.
Postelix writes into its own property group, called Postelix, and creates it on first use. Where a row names a property, it is the internal name your HubSpot admin sees.
| Object | HubSpot name | What it carries | Direction |
|---|---|---|---|
| Contact | postelix_signal | The latest signal: viewed a profile, commented, reacted, reposted, followed your company page, engaged with a promoted post or accepted a connection request | To HubSpot |
| Contact | postelix_signal_source | Where it happened: your company or connected voices, a competitor, or a market conversation | To HubSpot |
| Contact | postelix_signal_detail, postelix_signal_url, postelix_signal_at | What the person did, the LinkedIn post it happened on, and when | To HubSpot |
| Contact | postelix_signals_30d | Their signals in the 30 days before the send, for lead scoring | To HubSpot |
| Contact | postelix_sent_at, postelix_first_sent_at, postelix_sent_by | When Postelix last and first wrote the contact, and whether the automatic send or a person sent it | To HubSpot |
| Contact | postelix_market, postelix_fit, postelix_fit_reason | The market, a fit score from 0 to 100, and why the person fits | To HubSpot |
| Contact | postelix_buying_role, postelix_committee_role | Their likely buying role and their role in the account’s buying committee. HubSpot’s own Buying role is filled too where it is blank | To HubSpot |
| Contact | postelix_linkedin_url, postelix_record_url, postelix_email_verification | The LinkedIn profile, the person’s record in Postelix, and whether the email is valid, catch-all or unverified | To HubSpot |
| Contact | firstname, lastname, jobtitle, company, email, hs_linkedin_url | Name, title, company, email and LinkedIn URL, filled only where HubSpot is blank. A new contact gets them all | To HubSpot, blanks only |
| Contact | Up to 5 fields you pick | A value you set, for example a lead source: on new contacts only, when the field is empty, or always | To HubSpot |
| Contact | Static list “Postelix: LinkedIn interest” | Every contact Postelix sends. You can rename it or switch it off | To HubSpot |
| Contact | Note | One per person and signal, on the contact’s timeline | To HubSpot |
| Contact | Contact lists you pick | Each list adds its people to your market, or keeps them out of every send | From HubSpot |
| Contact | hubspot_owner_id, lifecyclestage, hs_lead_status | Owner, lifecycle stage and lead status, shown on the person in Postelix | From HubSpot |
| Contact | notes_last_contacted, notes_next_activity_date, num_contacted_notes, hs_sequences_is_enrolled | Last and next touch, the number of sales touches, and whether the person is in a sequence | From HubSpot |
| Contact | Emails, calls, meetings, notes, tasks, messages | Type, time, owner, direction, subject and outcome of the newest 20 within 12 months. Never the body | From HubSpot |
| Owner | Owners | Name and email, matched to your teammates by email | From HubSpot |
| Company | Company lists you pick, or all target accounts | Their companies become watched accounts, or everyone there is kept out | From HubSpot |
| Company | name, domain, linkedin_company_page, hubspot_owner_id, lifecyclestage, hs_is_target_account, hs_ideal_customer_profile | Matched to the account in Postelix by LinkedIn page or domain, with owner, stage, target account flag, tier and open deals | From HubSpot |
| Company | Company record (Add to CRM) | When a teammate clicks Add to CRM on an account alert: the company is found by domain or LinkedIn page, or created with name, domain and LinkedIn page when HubSpot has none, and its key people are linked to it | To HubSpot |
| Company | postelix_competitor_active, postelix_competitor_stage, postelix_competitor_people, postelix_competitor_last_seen, postelix_competitor_contested, postelix_competitor_customer_of | With Competitor Radar: which competitors’ sales teams are working the account, how far they got, how many people they engaged, and when | To HubSpot |
| Deal | Open deals | Name, stage, amount and close date, up to 5 per contact. A contact with an open deal is not sent | From HubSpot |
| Deal | postelix_competitor_active, postelix_competitor_last_seen | With Competitor Radar: the competitors in play and their latest touch, on the open deals of that company. A deal that closes keeps what it had | To HubSpot |
The contact Postelix wrote before, if its record link, email or LinkedIn URL still proves it is the same person.
The contact that holds the person’s email address.
Exactly one contact whose LinkedIn field holds the profile, in any of 12 spellings. With two or more, nothing is written.
Before Postelix writes to a contact HubSpot already holds, it checks it live. A customer or a contact with an open deal is skipped.
A contact counts as a customer at the lifecycle stage customer. On a match, Postelix fills only blank names, title, company and LinkedIn URL, and writes its own fields. If HubSpot answers that the email already exists because someone created the contact a moment earlier, Postelix fills blanks on that contact instead of creating a second one.
With automatic sending on, each cycle sends the people with a new signal in the last 30 days who have not been sent for it yet. Every hour Postelix reads HubSpot back: people with a recent signal every hour, everyone else once a day. A new or changed list is read within the hour, every list at least every 6 hours. You can also send selected people by hand, or press Sync with HubSpot now.
Who does what, from the first click to automatic sending.
In Settings, Connections, the Postelix workspace owner picks a market and clicks Connect HubSpot.
A user with Super Admin or App Marketplace access signs in to the right portal and accepts.
Sources and signals, the list name and up to 5 field values. Turn off Create new contacts to update existing ones only.
Up to 20 contact or company lists per market, each added to the market or kept out.
Postelix matches HubSpot owners to teammates by email. You can change any match.
Preview who is sent next, send 5 to 10 people by hand, check them in HubSpot, then switch on Send automatically.
Fewer permissions: if your security review needs it, Postelix can set up your workspace with a reduced HubSpot connection of seven permissions: contacts and their properties, lists, and reading deals. It sends contacts, the list and notes, reads contact lists and keeps people with an open deal out. It does not read companies, owners or sales history.
The HubSpot integration is part of the one Postelix plan: EUR 1,490 a month per market, everything included, with unlimited users. Nothing is charged per record. Teams start with a demo with the founder, then three months with integration, onboarding and training included for EUR 4,470. Prices exclude VAT where applicable. The details are on the pricing page.
For AI processing you choose an EU or a US route.
CRM connections use OAuth through Nango, which holds the credential.
Activity is read as type, time, owner and subject.
Older activity is deleted on every read.
They follow your portal’s setting for contacts from integrations, which is non-marketing unless you change it.
The HubSpot contacts, companies, activity and owners Postelix read are deleted. What it wrote stays in HubSpot.
Both are on the subprocessor list. Hosting and access are on the security page.
Yes, with different data in each direction. Postelix writes contacts, its own fields, a static list and timeline notes into HubSpot. It reads your lists, owners, lifecycle stages, open deals, companies and activity back. The Postelix fields go one way: a change you make to one of them in HubSpot does not flow back.
Sixteen scopes: read and write on contacts, companies and deals and on their property definitions, read and write on lists, read on owners, and sales-email-read for the subject and time of emails. Write on companies is used for the Competitor Radar fields and for Add to CRM, write on deals only for the Competitor Radar fields. A reduced connection with seven scopes is available.
Two roles. The Postelix workspace owner starts it, and a HubSpot user with Super Admin or App Marketplace access signs in to the right portal and accepts the permissions. One person can hold both.
No. HubSpot makes every permission Postelix asks for available to all accounts, free ones included (HubSpot’s scope reference, read on 21 November 2026). Where your plan sets a limit, for example on custom properties, a field HubSpot refuses is left out and the rest is still written.
No. It is part of the one Postelix plan, EUR 1,490 a month per market, and nothing is charged per record. On the HubSpot side, the contacts Postelix creates follow your portal’s setting for contacts from integrations, which is non-marketing unless you change it.
Yes, because routing stays in HubSpot. When Postelix sends a contact, it does not set an owner and does not change one. A new contact arrives with the Postelix fields and joins the static list, so your HubSpot workflows or your routing tool assign it by their own rules, for example on the list, on Postelix signal source or on the fit score.
It looks for the person in a fixed order before it writes: the contact it wrote before, if that still proves to be the person, then the email, then exactly one contact holding the LinkedIn URL. More than one LinkedIn match is refused, never guessed. If HubSpot reports that the email already exists, Postelix fills blanks on that contact instead of creating a second one.
New interest goes out every 30 minutes once automatic sending is on. HubSpot is read back every hour for people with a recent signal and once a day for everyone else, and every list you picked at least every 6 hours.
Yes. Choose competitors as a source under Send interest to HubSpot. People who comment on, react to or repost your competitors’ posts reach HubSpot with Postelix signal source set to A competitor, so a workflow can route them on their own. How Postelix finds them is on the competitor engagers page.
No. Postelix connects to HubSpot itself and does not use LinkedIn’s CRM Sync. Sales Navigator or Premium matters only for profile views: a connected LinkedIn account needs one of them for Postelix to see who viewed it. Comments, reactions and reposts come in without either.
No. Before it writes to a contact HubSpot already holds, Postelix checks the lifecycle stage and open deals live. A customer or a contact with an open deal is skipped, and later cycles leave the person out. People on a keep-out list from HubSpot are left out of every send.
Harvest the buyers your marketing already warmed up.