Estimated reading: 8 minutes 23 views

Pointics Integration as a Trigger

TL;DR: To set up the Pointics integration as a trigger in Bit Integrations, click Create Integration, search for and select Pointics on the trigger screen, open Select a Form/Task Name, and pick an event such as Tier Changed, then click Fetch.

Produce that same event in Pointics within the three-minute window, check the captured fields, and click Set Action. You need Bit Integrations Pro and the Pointics plugin active on the same WordPress site. The setup runs in six steps and takes about five minutes.

Pointics is a loyalty and rewards plugin for WordPress. It keeps a permanent log of every point your customers earn or spend, and builds earning rules, membership levels, a rewards catalogue, and a referral program on top of that log.

Pointics stores all of that on your WordPress site, away from your email, CRM, and spreadsheet tools. Bit Integrations connects Pointics to those tools.

A loyalty event can then start an action in another app with no manual work: add a member to a Mailchimp audience when they reach a new level, or log each committed redemption as a row in Google Sheets.

A completed referral can create a Bit CRM contact, and the points expiry sweep can post an alert in your Slack support channel.

How the Pointics Trigger Works

Bit Integrations follows a simple two-part model. The trigger is what happens. The action is what you want to happen next.

Trigger: an event inside Pointics, such as Points Earned or Tier Changed.
Action: one or more destination apps that receive the data, such as Google Sheets, Slack, Mailchimp, Fluent CRM, Airtable, Telegram, or other supported platforms.

When a trigger event happens in Pointics, Bit Integrations collects the record and its field data, then sends each value to the matching field in the connected app.

The process runs on your WordPress site, so your member data does not pass through a third-party automation service.

Before You Start

Bit Integrations is installed and activated on your WordPress site.
Bit Integrations Pro is active. Pointics is a Pro trigger, so the card does not appear without it.
Pointics is installed and activated on the same site.
Your Pointics program already has at least one earning rule, reward, level, or referral link, so you can produce a real event during setup.
You know which destination app you want to send data to, and you have its credentials or API key ready.

How to Set Up the Pointics Integration in Bit Integrations

The whole setup takes 6 steps. Follow them in order, because the fetch step in the middle depends on a live Pointics event that you create yourself while Bit Integrations is listening.

Step 01: Open Bit Integrations and Click Create Integration

From your WordPress dashboard, go to Bit Integrations. On the welcome screen or the integrations list, click the Create Integration button. The trigger selection page opens.

Step 02: Search and Select Pointics on the Trigger Screen

You land on the Please select a Trigger screen. Type Pointics into the Search Trigger… box and click the Pointics card when it appears.

Step 03: Choose Your Pointics Trigger Event

Open the Select a Form/Task Name dropdown and pick the trigger event you want to listen for. Pick the one that matches the exact moment you want your automation to start.

Points Events

Trigger Event	When It Fires
Points Earned	Fires every time points are credited to a member, whether an earning rule paid them out automatically or an administrator granted them by hand. The payload carries the ledger entry and the member behind it.
Points Adjusted	Fires when an administrator changes a balance manually from Pointics → Customers. The payload marks the change as a credit or a debit.
Points Expired	Fires once per expiry sweep, after the scheduled job expires at least one points lot. The payload carries the number of lots expired and the sweep time, not a member record.

Earning Rule Events

Trigger Event	When It Fires
Channel Awarded	Fires when one of your earning rules pays out for a customer action. Bit Integrations calls the rule a channel, and the payload names the channel that paid, along with the points it awarded.

Popular starting points:

Points Earned for mirroring every credit into a spreadsheet or a CRM record.

Step 04: Click the Fetch Button

After you select an event, a Fetch button appears. Click it. Bit Integrations now starts listening for a real Pointics record so it can learn that event’s field structure.

Warning: Points Expired only fires from the scheduled expiry sweep, so you cannot produce it on demand inside the fetch window. To build a flow on that event, fetch the fields with a different event first, or run the fetch when you know a sweep is due.

Step 05: Create a Test Record Within the 3 Minute Window

The Fetch button changes to a spinning Waiting for form submission… state with a three-minute countdown. During that window, go and perform in Pointics the exact action you selected in Step 03.

The test record must match the trigger event you chose:

Points Earned or Channel Awarded: complete the customer action one of your earning rules pays for, such as a test order.

If the countdown ends before your test event lands, nothing is broken. Click Fetch again and repeat the action.

Warning: Only flat values reach the field table. Pointics stores extra detail inside a nested meta block on a ledger entry, and that block is dropped, so points breakdowns and channel meta never appear as mappable fields. Build your action on the top-level fields you can see in Step 06.

Step 06: Review the Fetched Data and Click Set Action

As soon as the test record is captured, the button turns into Fetched ✔ and a field table appears. Every field from that record is listed with its detected data type, and the sample values from your test event are shown alongside.

Check that the fields you care about are there (for example, points, user_email, display_name, and created_at), and adjust any data type from its dropdown if the detected type isn’t what you want.

You are now on the action setup screen. Search for your destination app, connect it, map the Pointics fields to the destination fields, and save the integration.

To confirm the flow works, produce the same Pointics event once more and open the integration’s log from the Bit Integrations list: the run appears there with a success status, and the record shows up in your destination app.

Narrow the flow further with Bit Integrations smart tags when you need dynamic values in the action fields.

Explore 3 Useful Pointics Integration Use Cases

Here are 3 integration ideas that solve real problems for small teams. Each one uses the same 6-step setup described above, with a different action app at the end.

Pointics Mailchimp Integration

A customer who reaches your top level is your best customer, and you find out weeks later when someone exports the list by hand. This automation puts them in the right audience the second they get there.

Trigger: Tier Changed
Action: Mailchimp adds or updates the member in an audience.
What it does: The event carries the member’s email address, display name, and the level they moved into, so Mailchimp can hold a VIP audience that keeps itself current. You stop exporting level lists by hand. Add a Bit Integrations condition on the direction field to act only on promotions and ignore demotions.
Watch out: Pointics sends the level as a numeric ID, not a name. Map it to a merge field and keep the name lookup on the Mailchimp side.

Pointics Slack Integration

Expiring points generate support tickets, and your team usually hears about the sweep from the first annoyed customer. This automation tells them first.

Trigger: Points Expired
Action: Slack posts a message to a support channel.
What it does: The sweep sends the number of points lots it expired and the time it ran, so the channel gets a running record of when balances dropped and by how many lots. Your team stops guessing why balances changed overnight. Point it at the same channel your helpdesk watches so the context is there when a ticket arrives.
Watch out: This event carries no member details. It reports a batch total, so it cannot be used to message the affected customers.

Pointics Airtable Integration

Manual point changes are the ones people ask about later, usually months later. This automation writes an audit trail as the changes happen.

Trigger: Points Adjusted
Action: Airtable creates a record in an adjustments table.
What it does: Every manual adjustment carries the points, the credit or debit direction, the description an administrator typed, and the member’s email address. Your support team can search who changed a balance and why without opening the ledger. Add a view filtered to debits to review the changes that take points away.

Pointics Integration as a Trigger

How the Pointics Trigger Works

Before You Start

How to Set Up the Pointics Integration in Bit Integrations

Step 01: Open Bit Integrations and Click Create Integration

Step 02: Search and Select Pointics on the Trigger Screen

Step 03: Choose Your Pointics Trigger Event

Points Events

Earning Rule Events

Step 04: Click the Fetch Button

Step 05: Create a Test Record Within the 3 Minute Window

Step 06: Review the Fetched Data and Click Set Action

Explore 3 Useful Pointics Integration Use Cases

Pointics Integration as a Trigger

Subscribe