Integration

Connect Aplos to Geckoboard

When something happens in Aplos, your agent does the next thing in Geckoboard. Describe it and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want Aplos and Geckoboard to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

Aplos holds the giving and contact records; Geckoboard shows numbers on a screen people actually look at. Joining them means each new contribution or contact in Aplos can push rows into a Geckoboard dataset, so the giving board, fund totals and donor counts come from the accounting system rather than a spreadsheet someone updates by hand.

Example flows

What Aplos can start in Geckoboard

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Aplos and Geckoboard

Triggers and actions 3 triggers · 18 actions

Each app on its own

Reviews

What our customers say

More from Aplos

More into Geckoboard

Questions

Aplos and Geckoboard, answered

Can the board show giving by purpose or fund?

Yes. A new contribution in Aplos can be read back with Get contribution to see its donor and purpose lines, and those lines can be appended to a Geckoboard dataset as separate rows. You can also list purposes or funds in Aplos first so only the ones you track reach the board.

Should the dataset be appended to or replaced?

Append Dataset Data adds rows and keeps the most recent ones, which suits a running list of contributions. Replace Dataset Data swaps everything for the rows you send, which suits totals that should be restated each time, such as fund or contact summaries.

What can start an automation from Aplos?

Any of Aplos's 3 triggers in the catalog, including New contact, New contribution and New or updated contact. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Geckoboard when something happens in Aplos?

Any of Geckoboard's 5 actions, including Append Dataset Data, Replace Dataset Data, Create or Update Dataset and Verify API Key. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Geckoboard to Aplos?

Geckoboard has no triggers in the catalog today, so automations start in Aplos. If you need the other direction, ask: your agent reads Geckoboard's API documentation and adds it.

Do I have to build a connector for Aplos or Geckoboard?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.