Fix Make.com/Parseur/Airtable Automation
Budget: £10 – £15 GBP
**Project: Fix and Stabilise Make.com → Parseur → Airtable Automation (Fish Price Lists)**
**Overview**
I run a seafood wholesale business and receive supplier price lists (PDFs and images) via email. I’ve built an automation using Make.com and Parseur to extract the data and send it into Airtable.
The system is partially working but currently unstable. I need an experienced Make.com/Airtable specialist to fix the data ingestion and make it reliable.
---
**Current Setup**
* Email → Make.com (watch emails + attachments)
* Attachments → Parseur (OCR/data extraction)
* Parsed data → Make.com → Airtable (table: Raw Fish Prices)
---
**Core Problem**
Airtable is rejecting values when creating records (422 error: “Field cannot accept the provided value”), specifically for the “Price per kg” field.
Likely causes:
* Data type mismatch (string vs number)
* OCR inconsistencies (e.g. £6.80 vs 680 vs 6,80)
* Formatting issues in Make mapping
---
**What I Need Fixed**
1. **Fix Airtable mapping**
* Ensure all numeric fields (especially Price per kg) are correctly formatted and accepted
* Eliminate 422 errors completely
2. **Clean price parsing**
* Remove currency symbols (£)
* Handle decimal issues (e.g. 680 → 6.80)
* Handle commas vs dots (6,80 vs 6.80)
* Handle blanks / invalid values safely
3. **Stabilise ingestion**
* Ensure all records are created without failure
* Add basic error handling (skip or default bad rows instead of crashing scenario)
---
**Nice to Have (optional but preferred)**
* Extract structured fields from item description:
* Species (e.g. Bass, Dory)
* Size (e.g. 1-2, 500-1)
* Clean and standardise output in Airtable
* Add simple validation flags (e.g. unusually high prices)
---
**Tech Stack**
* Make.com (Integromat)
* Parseur (document parsing)
* Airtable
---
**Access**
I can provide:
* Access to Make scenario
* Airtable base
* Sample supplier files
---
**Outcome Required**
* Fully working automation
* No Airtable errors
* Clean numeric data stored correctly
* System reliable for daily use
---
**Time Expectation**
This should be a relatively small job for someone experienced (estimate 2–4 hours).
---
**Bonus**
If the work goes well, there may be follow-on work to build:
* Pricing comparison vs market data
* Automated daily reports for customers
**Overview**
I run a seafood wholesale business and receive supplier price lists (PDFs and images) via email. I’ve built an automation using Make.com and Parseur to extract the data and send it into Airtable.
The system is partially working but currently unstable. I need an experienced Make.com/Airtable specialist to fix the data ingestion and make it reliable.
---
**Current Setup**
* Email → Make.com (watch emails + attachments)
* Attachments → Parseur (OCR/data extraction)
* Parsed data → Make.com → Airtable (table: Raw Fish Prices)
---
**Core Problem**
Airtable is rejecting values when creating records (422 error: “Field cannot accept the provided value”), specifically for the “Price per kg” field.
Likely causes:
* Data type mismatch (string vs number)
* OCR inconsistencies (e.g. £6.80 vs 680 vs 6,80)
* Formatting issues in Make mapping
---
**What I Need Fixed**
1. **Fix Airtable mapping**
* Ensure all numeric fields (especially Price per kg) are correctly formatted and accepted
* Eliminate 422 errors completely
2. **Clean price parsing**
* Remove currency symbols (£)
* Handle decimal issues (e.g. 680 → 6.80)
* Handle commas vs dots (6,80 vs 6.80)
* Handle blanks / invalid values safely
3. **Stabilise ingestion**
* Ensure all records are created without failure
* Add basic error handling (skip or default bad rows instead of crashing scenario)
---
**Nice to Have (optional but preferred)**
* Extract structured fields from item description:
* Species (e.g. Bass, Dory)
* Size (e.g. 1-2, 500-1)
* Clean and standardise output in Airtable
* Add simple validation flags (e.g. unusually high prices)
---
**Tech Stack**
* Make.com (Integromat)
* Parseur (document parsing)
* Airtable
---
**Access**
I can provide:
* Access to Make scenario
* Airtable base
* Sample supplier files
---
**Outcome Required**
* Fully working automation
* No Airtable errors
* Clean numeric data stored correctly
* System reliable for daily use
---
**Time Expectation**
This should be a relatively small job for someone experienced (estimate 2–4 hours).
---
**Bonus**
If the work goes well, there may be follow-on work to build:
* Pricing comparison vs market data
* Automated daily reports for customers