Issue sending bundles from Iterator to Airtable to create multiple lines

:bullseye: What is your goal?

I’m building an automated receipt-processing and tax-management workflow in Make.
The workflow starts with a file sent to my Telegram bot.
It then extracts text, sends it to OpenAI for structured JSON, parses the JSON, iterates over the line items (only for rental income statements), and finally creates separate Airtable records for each item (from the rental income statement).
My goal
I want a completely automated flow that:
Receives a receipt/statement via Telegram
Extracts text
Sends the text to OpenAI
Gets properly formatted JSON (multiple line items)
Iterates over each line item
Sends each line item to Airtable as an individual record

:thinking: What is the problem & what have you tried?

The iterator is separating the information into multiple bundles. However, when it gets to the Airtable module (which is next), it only receives the first bundle and therefore creates one line. It does not continue over the rest of the bundles. There is no filter between the iterator and Airtable. There is no other module between the two. There is nothing else happening between those two modules. I have managed to delete the Airtable, reinstall it as a module, and then it works for one run-through of the whole flow. However, when I run it through again, it always stops and only comes up with the first bundle.

:clipboard: Error messages or input/output bundles

I’m not getting any errors. The bundles are being sent, but just not being iterated over.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

You can try adding an Aggregator after your Iterator and use Airtable (Bulk Create Records) instead of Airtable (Create a Record).

Welcome to the Make community!

The output bundle looks correct, so the issue’s probably somewhere else in your scenario.

We’d love to help, however, we require more information that demonstrates the problem to help us reproduce the scenario and any issues and errors.

1. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

  • the full scenario, and the zoomed in parts of the scenario that you are referring to (if your scenario is huge),
  • a full scenario run/execution from the history (showing output “speech” bubbles),
  • relevant module fields (showing how you’ve used any built-in functions, and how you’ve mapped the variables),
  • relevant filters between modules (showing which operators and any built-in functions you’ve used, and how you’ve mapped the variables),
  • relevant module input/output bubbles,
  • if applicable, any error messages,
  • and if applicable, any external services (spreadsheet headers/ sample data/ regex101.com/ etc. to show the item/ record exists, and is set up correctly).
Need help❓View instructions ◀

We would appreciate it if you could directly upload screenshots here instead of linking to them outside of this forum. This allows us to zoom in on the image when clicked, and also having improved privacy from third-party sources.

Taking Screenshots

  • Microsoft Windows: Take screenshots using the “Windows Snipping Tool”, by pressing either PrtSc or WinShiftS keys on your keyboard.
  • MacOS: Take screenshots by pressing CommandShift4 keys on your keyboard.

Uploading Attachments

  • Drag image files directly into the rich-text editor, or
  • Click on the upload button in the editor toolbar to select files:

2. Scenario Blueprint

Providing your scenario will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return. This would benefit you in implementing our suggestions as you can view screenshots of the changes or paste corrected modules back into your scenario.

Need help❓View instructions ◀

A. Export Blueprint

In the scenario editor, click the three dots at the top-right, then select “Export blueprint”.

  • You can upload files and images to this forum by clicking on the upload button:

    Uploading an attachment here will look like this:
    blueprint.json (12.3 KB)

B. Create Public Share Link

In the scenario editor, click on the Share button:

Read more about the scenario sharing feature in the Help Centre.

3. Output Bundles (properly formatted!) from Scenario Run

Please provide the output bundles (input bundles are not so crucial) of each of the relevant modules by running the scenario, or get output bundles from a previous scenario run from the “History” tab.

Providing the output bundles will allow others to replicate what is going on in the scenario, especially if there are complex data structures (nested arrays and collections), especially if external services are involved, and help you with mapping the raw property names from collections.

Need help❓View instructions ◀

Click on the white speech bubbles on the top-right of each module and select “Download output bundles”.

A. Upload a Text File

Save each bundle contents in a plain text editor as a bundle.txt file. Open the file to check if it has not added additional formatting or encoded the plain text.

  • You can upload files and images to this forum by clicking on the upload button:

    Uploading an attachment here will look like this:
    output-bundle.txt (12.3 KB)

B. Insert a Formatted Code Block

If you are unable to upload files on this forum, alternatively you can paste the bundles AND format them correctly.

:warning: Formatting IS Important! :warning:

Here are some ways to provide text content in a way that it won’t be modified by the forum.

  • Method 1: Type code fence manually
    Manually type three backticks ``` in a separate line before and after the content, like this,

    ```
    text goes here
    ```
    
  • Method 2: Highlight the pasted content, then click the preformatted text/code button

  • Method 3: Upload your file elsewhere and share the public link
    This method is only advised for large files exceeding the forum upload limit.

Sharing these details will make it easier for others to assist you, so that you can get better answers, faster.

Hope this helps! If you are still having trouble, please provide more details.

@samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!