Archive Inactive Partners
Reads active partners from Odoo, calculates how many days have passed since each record was last updated, and automatically archives those that have been inactive beyond a configurable threshold — keeping your contact database clean without manual intervention.
This pipeline runs on a schedule and automatically archives Odoo partners that have had no activity for longer than a configurable number of days. Archived records are hidden from default Odoo views but remain in the database — nothing is deleted. Set the threshold once and your contact list stays clean without anyone having to touch it.
active = False in Odoo hides the record from default views but does not delete it. You can unarchive any record manually or by running a reverse pipeline. Review the filter parameters before the first production run.
res.partner excluding any record linked to an active internal user — user_ids = False. This prevents the pipeline from attempting to archive partners that Odoo would reject because they have an active login account attached.write_date — the timestamp of the last modification to the record — and calculates how many days have elapsed since then. The result is added to the stream as the integer field days_inactive.INACTIVITY_DAYS pipeline parameter and adds it to the stream as inactivity_days. FilterRows then keeps only the partners whose days_inactive exceeds that value. All others pass through without being touched.active = false to each qualifying row. The Putki Odoo Update plugin writes that value to Odoo using the partner's internal id as the key — setting active = False on res.partner and archiving the record. Records are processed in batches of 100.res.partner, plus your database URL and API key. The Odoo user must have permission to archive records.INACTIVITY_DAYS to a small value on first run and review which records are selected before running at full scale. The default is 365 days — adjust the search domain to match your definition of inactive if needed.Archive Inactive Partners
Reads active partners from Odoo, calculates how many days have passed since each record was last updated, and automatically archives those that have been inactive beyond a configurable threshold — keeping your contact database clean without manual intervention.
This pipeline runs on a schedule and automatically archives Odoo partners that have had no activity for longer than a configurable number of days. Archived records are hidden from default Odoo views but remain in the database — nothing is deleted. Set the threshold once and your contact list stays clean without anyone having to touch it.
active = False in Odoo hides the record from default views but does not delete it. You can unarchive any record manually or by running a reverse pipeline. Review the filter parameters before the first production run.
res.partner excluding any record linked to an active internal user — user_ids = False. This prevents the pipeline from attempting to archive partners that Odoo would reject because they have an active login account attached.write_date — the timestamp of the last modification to the record — and calculates how many days have elapsed since then. The result is added to the stream as the integer field days_inactive.INACTIVITY_DAYS pipeline parameter and adds it to the stream as inactivity_days. FilterRows then keeps only the partners whose days_inactive exceeds that value. All others pass through without being touched.active = false to each qualifying row. The Putki Odoo Update plugin writes that value to Odoo using the partner's internal id as the key — setting active = False on res.partner and archiving the record. Records are processed in batches of 100.res.partner, plus your database URL and API key. The Odoo user must have permission to archive records.INACTIVITY_DAYS to a small value on first run and review which records are selected before running at full scale. The default is 365 days — adjust the search domain to match your definition of inactive if needed.