Resources · Zapier integration

Absinthe Zapier integrationAutomate Absinthe with Zapier.

The Absinthe Zapier integration gives you 0 triggers, 1 action and 0 searches. One move only: credit points to someone in your Absinthe points program when something happens in another app. Here is how it works, what it costs and where it fails.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Absinthe Zapier integration actually does

Absinthe runs points programs for Web3 projects. Connecting it to Zapier lets another app hand out those points for you: something happens elsewhere, and Absinthe credits the right person with the right amount. It works one way only. Absinthe receives, it never starts anything.

Three results people build with the single action, Issue Points:

A spreadsheet that pays out. A community manager keeps a sheet of people who joined a call. Each new row carries a wallet address and a score, and the Zap turns that row into points without anyone copying numbers by hand.

Rewards for an off-chain chore. A bug report, a translation, a survey answer: work that never touches the blockchain can still earn points, as long as some app records it and Zapier can see it.

One registered event, many sources. Every point you issue is tied to an event you first register inside Absinthe. Several Zaps can feed the same event, so a quest that spans a form and a sheet still adds up in one place.

What Zapier does not do here: it cannot tell you when something changes inside Absinthe, because the app offers no trigger. It cannot look up a user or read a balance either, since there is no search. And it cannot register the event for you; that step happens in Absinthe first. If you are still choosing a tool, read the Make vs Zapier comparison before you build.

Vocabulary

Zapier words you will meet on this page

Seven terms. Learn them once and the rest of the page reads easily.

Zap
The automation you assemble in Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event in an app that sets the Zap off. Absinthe has none, so your trigger always comes from another tool.
Action
What the Zap does once it is running. With Absinthe, the only action is crediting points to an account.
Task
The unit Zapier bills: one action that completes successfully. Your plan's monthly count is a count of these.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app the moment the event occurs.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Connection
Your Absinthe account linked to Zapier once, then reused by every step that talks to Absinthe.
Cost

What it really costs

Absinthe is not a premium app, so it works on the free plan. The bill depends on how many points you issue, not on how often Zapier looks.

  • Tasks on the free plan100 per month
  • Free plan Zap size1 trigger + 1 action
  • Premium appNo
  • Billed perSuccessful Issue Points run

The trigger never costs a task, and checking for new data costs nothing however often it happens. Each successful Issue Points run counts as one task; a failed one is not counted. The free plan gives you 100 tasks a month and two-step Zaps only: one trigger, one action. Add a filter (say, to skip rows with no wallet) and the Zap becomes multi-step, which means a paid plan. Plan your volume of points before you pick a tier.

Connect

Connect Absinthe to Zapier in three steps

  1. 01

    Open your connections

    In your Zapier account, go to Apps, then click + Add connection. You need an Absinthe account first, plus access to any project you do not own yourself.

  2. 02

    Pick Absinthe

    Type Absinthe in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Absinthe side, where the sign-in happens.

  3. 03

    Sign in and grant access

    Log in to Absinthe in that tab and allow Zapier to act on the account. The connection then appears in your list, and every Absinthe step in every Zap reuses it.

First Zap

Your first Zap: points for every new sheet row

GoalEach row added to a contributors sheet credits points to the wallet written in that row.

  1. 01

    Start the Zap from the sheet

    Create a Zap and choose your spreadsheet app as the trigger. Point it at the sheet where each contributor gets one row, with a wallet column and a points column.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent rows of the connected account, so you map fields on real data rather than guesses.

  3. 03

    Add Issue Points

    Add Absinthe as the action and pick Issue Points. Map the wallet column to Account ID and the score column to Points Amount, then paste your Registered Event ID.

  4. 04

    Test, then publish

    Test the action once and check the credit in Absinthe. If it landed, click Publish. From then on, only rows added after that moment are picked up.

Actions

The Absinthe action

Absinthe gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Issue Points

Action

In Zapier“Issues points to a user's account for completing an off-chain action”

Credits a chosen number of points to one account in your Absinthe program, tied to an event you registered beforehand. It is the only thing Zapier can do in Absinthe.

When to use it
a contributor finishes a task tracked outside the chain, such as a survey or a review, and should see it rewarded.
Watch out
the Account ID must match the identity type you chose in Absinthe, so an email will not land where a wallet address is expected.
When it breaks

When the Zap breaks

Zapier publishes no help article for Absinthe, so the failures below are the general ones. They still bite.

Most trouble comes from the trigger side, since that app decides what reaches Absinthe. If a Zap misbehaves, start with the Zapier troubleshooting page.

  • Past activity is never rewarded

    A Zap only reacts to what happens after you switch it on. Rows or entries that already existed earn nothing; paying them out is a separate job.

  • A Zap that feeds itself

    If your Zap writes back into the very place its trigger watches, it sets itself off again and again and burns through your task count quickly.

  • Bulk imports get held back

    Paste hundreds of rows at once and the trigger may return a huge batch. Zapier's flood protection can hold it back before any points go out.

  • Duplicates are filtered out

    On a polling trigger Zapier remembers what it has already seen, so an unchanged row does not start the Zap twice or credit points twice.
Need help

Need help automating Absinthe with Zapier?

A person reads every message.

FAQ

Absinthe Zapier integration: common questions

01Is the Absinthe Zapier integration free?
Yes, you can use it on the free plan. Absinthe is not a premium app, so Zapier does not lock it behind a paid tier. The free plan does come with limits: 100 tasks a month and Zaps of two steps only, meaning one trigger followed by one action. A simple Zap that awards points for each new form answer fits inside that. As soon as you add a filter or a second action, the Zap counts as multi-step and you need a paid plan. Check how many points you expect to issue per month before you commit.
02How many tasks does awarding points use?
One task per successful Issue Points run. The trigger costs nothing, and neither do the checks Zapier makes to find new data. So if fifty people complete a quest and each completion credits points once, that is fifty tasks. A run that fails is not counted against your plan. If you later add a second action, say a message to the contributor, each successful action counts on its own, which doubles the bill for the same activity. Keep that in mind on the free plan, where the ceiling sits at 100 tasks a month.
03Does Absinthe react in real time?
Absinthe has no trigger of its own, so the speed depends on the app that starts your Zap. If that app offers an instant trigger, it tells Zapier as soon as the event happens and points go out right away, whatever your plan. If it uses a polling trigger, Zapier checks on a timer: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. Pick a starting app with an instant trigger when speed matters to your community.
04What does it take to connect Absinthe to Zapier?
An Absinthe account, and access to any project you do not own yourself. In Zapier you open Apps, click + Add connection, search for Absinthe and sign in on the tab that opens, then grant access. Before building, also register the event you want to reward inside Absinthe. Issue Points cannot run without that event's ID, which Absinthe shows in its API sidebar once the event exists. Without it the action has nothing to attach the points to.
05Why do points not reach the right user?
Usually because the Account ID does not match the identity type set in Absinthe. That field expects whatever identifier your program uses: a wallet address in one setup, an email in another. If your form collects emails but the program expects wallet addresses, the credit goes nowhere useful. Map the column that holds the right kind of identifier, and test the action once on a real record before you publish. Points Amount must also be a number of zero or more, never text.
06What if the Absinthe operation you need is missing?
Zapier offers a single operation for Absinthe: Issue Points. There is no trigger to watch Absinthe, no search to look up a user and no action to remove points. If your workflow needs any of those, Zapier cannot do it with the current connection. The realistic options are to rethink the flow so that awarding points is the only Absinthe step, or to handle the rest directly inside Absinthe. Recheck the app page from time to time, as the list of operations can grow.
07Zapier, Make or n8n for Absinthe?
It depends on your criteria rather than on a winner. Zapier is the quickest start when you only need to award points from a tool it already connects to, and the free plan covers a simple two-step Zap. Make and n8n become worth comparing when your flow needs a filter or several actions, since multi-step Zaps require a paid plan. Look at which of your other tools each platform supports and at how your volume of points translates into billing on each.
Same platform

Other docs you might need on this stack.

Browse all integrations