Resources · Make integration

Citibank Make integrationAutomate Citibank with Make.

Got Citibank Account Alert emails piling up with details you retype by hand? The Citibank Make integration gives you 1 module that reads the text of those alerts and hands the result to the next step. Below you'll see what it does, how to connect it and how to build a first scenario.

Try the Citibank integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Citibank Make integration do?

The Citibank Make integration is a single transformer module that processes the text of a Citibank Account Alert email and makes its content available to the modules that follow. In Make, a scenario is the automation you build, and a module is one brick of it. This one does not watch your bank: it works on alert text another module brings in.

A tidier finance log is the most common goal. An email app earlier in the scenario picks up the alert, Parser of Account Alert email messages processes its text, and the output travels on as a bundle (one item passed from module to module) to a sheet or a database.

A faster heads-up for the team is the second pattern. Once the alert text is parsed, a messaging module downstream can post a short notice to the people who need it, so nobody has to forward the raw email.

A cleaner handoff to accounting is the third. The parsed output can feed whatever tool your bookkeeper already uses, keeping the alert in a structured shape instead of a block of prose.

What this integration does not do matters just as much. It has no trigger, no action on the account and no Make an API Call module, so it cannot read balances or move money. The documentation gives no numeric limit either. The same app often has an n8n node too; the n8n vs Make comparison lays out both tools, and the Make review covers the editor itself. If a parse goes wrong, Make troubleshooting is the place to start.

Connect

How do you connect Citibank to Make?

  1. 01

    Add the Citibank module

    In your scenario, click the + and search for Citibank, then pick Parser of Account Alert email messages. If Make asks for a connection, meaning your account linked to Make once and reused by every module of the app, click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, but a clear label helps later when a teammate opens the scenario and wonders which account or mailbox it relies on.

  3. 03

    Authorize and save

    Authorize Make on the page that opens, or paste the key you were given, then click Save. The Citibank documentation lists no specific prerequisite, so these are the generic Make steps.

First scenario

Build your first scenario with Citibank

GoalWhen a Citibank Account Alert email lands, Make parses its text and passes the result to the next app.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Here that first module belongs to the app where your alert emails arrive.

  2. 02

    Bring in the alert email

    Pick the module of that other app that receives the message and create its connection. Make lists the folders it can read once the account is linked, so choose the one holding your alerts.

  3. 03

    Add the Citibank parser

    Click the + on the right of that module, search for Citibank and add Parser of Account Alert email messages. Map the email text from the previous module into it.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles each module received and check that the parser output looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From then on each run counts operations, one per module per bundle, on your plan.

Modules

What the Citibank module does in Make

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

Citibank1

Parser of Account Alert email messages

Transformer

In Make“Processes text of Account Alerts. The output data is then available for further use.”

This transformer takes the text of a Citibank Account Alert email and returns it as output data the rest of your scenario can map, ready to store, forward or sort.

When to use it
right after the module that fetches the alert email, whenever the next step needs the alert content rather than the whole message.
Watch out
it reads text only and does not connect to your bank account, so it cannot fetch anything the email itself does not contain.
Need help

Need help automating Citibank with Make?

A person reads every message.

FAQ

Citibank Make integration: common questions

01Is the Citibank Make integration free?
Yes. Citibank is a standard app, so it is available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, which are operations, per month. Every time the parser processes one alert, that is one operation.
02What do you need to connect Citibank to Make?
The Citibank documentation lists no specific prerequisite, so the generic Make flow applies. Add the Citibank module to a scenario, click Create a connection if Make asks for one, optionally give it a name, authorize Make on the page that opens or paste the key you were given, and click Save. Just as important, you need a module from another app that brings in the Account Alert email, because the parser only works on text it receives from an earlier step in the scenario.
03Does the Citibank Make integration react in real time?
No, not by itself. Citibank has no trigger in Make, so the parser never starts a scenario. The scenario starts from the first module, which belongs to another app, typically the one where your alert emails arrive. That first module runs on the scenario schedule, every 15 minutes by default, or as soon as its own app calls Make if it is an instant trigger. On the Free plan the shortest scheduled interval is 15 minutes; paid plans go down to 1 minute.
04What if the Citibank module does not do what you need in Make?
It depends on the need. The integration has a single module, the Account Alert parser, and no Make an API Call module, so there is no universal fallback inside the Citibank app. If you need to act on the account itself, this app cannot do it; look for another app in Make that covers that job. If the parser is right but the result needs reshaping, the next modules in the scenario can handle it. For a setup that goes further, the team can help you scope it.
05Should you use Make or n8n for Citibank?
It depends on the tool your team already works in. The same app often has an n8n node, so the choice rarely comes down to Citibank itself. On the Make side, you get one parser module, a visual editor where you test with Run once, and a Free plan with 2 active scenarios. Compare which of the two tools your other apps and your colleagues already rely on, then build the scenario there. Neither tool is ranked here: pick the one your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations