PHPackages                             divanteltd/pimcore-auto-import - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. divanteltd/pimcore-auto-import

ActivePimcore-bundle

divanteltd/pimcore-auto-import
==============================

Auto Import runs Import Definitions automatically on created assets

1.0.0(5y ago)11.6kGPL-3.0-or-laterPHP

Since Oct 30Pushed 5y ago7 watchersCompare

[ Source](https://github.com/DivanteLtd/pimcore-auto-import)[ Packagist](https://packagist.org/packages/divanteltd/pimcore-auto-import)[ Docs](https://www.divante.com)[ RSS](/packages/divanteltd-pimcore-auto-import/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (1)Dependencies (2)Versions (2)Used By (0)

AutoImport for Pimcore
======================

[](#autoimport-for-pimcore)

This bundle allows running DataDefinitions () imports automatically for created assets.

Installing
----------

[](#installing)

```
composer require divanteltd/pimcore-auto-import
```

Enable and install the Bundle in admin panel or in command line:

```
./bin/console pimcore:bundle:enable AutoImportBundle
./bin/console pimcore:bundle:install AutoImportBundle
```

EventListeners
--------------

[](#eventlisteners)

Bundle listens on event:

- `pimcore.asset.postAdd` - handled by \\Divante\\AutoImport\\EventListener\\AssetEventListener::onPostAdd
- `import_definition.*` - handled by \\Divante\\AutoImport\\EventListener\\ImportDefinitionsEventListener

Requirements
------------

[](#requirements)

- ProcessManager ()
- DataDefinitions ()

Usage
-----

[](#usage)

After installation open up Website settings and fill in:

- `AutoImport_INTEGRATION` - integration name
- `AutoImport_DEFINITION` - name of the Import Defintion
- `AutoImport_FOLDER` - folder which bundle will monitor for incoming files

[![Website settings example](docs/img/website-settings.png?raw=true)](docs/img/website-settings.png?raw=true)

From now on, all assets added to the configured folder (`product` in example above) will be used as an input to defined Import Definition. Executable in Process Manager will be createad automatically, alongside with additional folder structure, as subfolders of the one defined in Website Settings (if needed):

- `/processing` - files being currently imported
- `/done` - files sucessfully imported
- `/error` - files which import ended with an error

[![Folder structure](docs/img/folder-structure.png?raw=true)](docs/img/folder-structure.png?raw=true)

Tips
----

[](#tips)

### Mutliple integrations

[](#mutliple-integrations)

You can define additional watch folders and definitions, by adding additional Website Settings:

- `AutoImport_INTEGRATION_sampleName` - last part is used to find other configuration lines
- `AutoImport_DEFINITION_sampleName`
- `AutoImport_FOLDER_sampleName`

### Automatize asset creation based on filesystem changes

[](#automatize-asset-creation-based-on-filesystem-changes)

If external system is uploading the file to the filesystem directly (not using admin panel, GraphQL or WebDAV), you can easily synchronize the filesystem changes using Pimcore Devkit ():

```
./bin/console devkit:asset:synchronize /ERP/ingoing
```

Using Process Manager's build-in cron functionality, you can easily run this command periodically.

### Two-way communication

[](#two-way-communication)

If your integration is entirely based on file exchange, you can use this bundle with Scheduled Export () to configure complete integration in Pimcore admin panel.

Contributing
------------

[](#contributing)

If you'd like to contribute, please fork the repository and use a feature branch. Pull requests are warmly welcome.

Licence
-------

[](#licence)

Pimcore Scheduled Export source code is completely free and released under the [GNU General Public License v3.0](https://github.com/DivanteLtd/divante-ltd/pimcore-scheduled-export/blob/master/LICENSE).

Standards &amp; Code Quality
----------------------------

[](#standards--code-quality)

This module respects all Pimcore code quality rules and our own PHPCS and PHPMD rulesets.

About Authors
-------------

[](#about-authors)

[![Divante-logo](https://camo.githubusercontent.com/bc1c14c75be0ef53c3c97ec254ff2503ecbe209e3785b48e111e7f82e0d5853a/687474703a2f2f646976616e74652e636f2f6c6f676f2d48472e706e67 "Divante")](https://camo.githubusercontent.com/bc1c14c75be0ef53c3c97ec254ff2503ecbe209e3785b48e111e7f82e0d5853a/687474703a2f2f646976616e74652e636f2f6c6f676f2d48472e706e67)

We are a Software House from Europe, existing from 2008 and employing about 150 people. Our core competencies are built around Magento, Pimcore and bespoke software projects (we love Symfony3, Node.js, Angular, React, Vue.js). We specialize in sophisticated integration projects trying to connect hardcore IT with good product design and UX.

We work for Clients like INTERSPORT, ING, Odlo, Onderdelenwinkel and CDP, the company that produced The Witcher game. We develop two projects: [Open Loyalty](http://www.openloyalty.io/ "Open Loyalty") - an open source loyalty program and [Vue.js Storefront](https://github.com/DivanteLtd/vue-storefront "Vue.js Storefront").

We are part of the OEX Group which is listed on the Warsaw Stock Exchange. Our annual revenue has been growing at a minimum of about 30% year on year.

Visit our website [Divante.com](https://divante.com/ "Divante.co") for more information.

###  Health Score

27

—

LowBetter than 49% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity17

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity53

Maturing project, gaining track record

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

2017d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/1809664?v=4)[Kuba Płaskonka](/maintainers/kubaplas)[@kubaplas](https://github.com/kubaplas)

---

Tags

pimcorepimcore-plugin

### Embed Badge

![Health badge](/badges/divanteltd-pimcore-auto-import/health.svg)

```
[![Health](https://phpackages.com/badges/divanteltd-pimcore-auto-import/health.svg)](https://phpackages.com/packages/divanteltd-pimcore-auto-import)
```

###  Alternatives

[coreshop/core-shop

CoreShop - Pimcore eCommerce

289197.5k10](/packages/coreshop-core-shop)[instride/data-definitions

Data Definitions allows you to define your DataObject Imports and Exports using a nice GUI and re-run the definitions as often you like.

8117.7k](/packages/instride-data-definitions)[dpfaffenbauer/process-manager

Process Manager helps you to see statuses for long running Processes

3289.3k2](/packages/dpfaffenbauer-process-manager)[youwe/workflow-gui

Workflow Configuration UI for Pimcore

2884.6k](/packages/youwe-workflow-gui)[divante-ltd/pimcore-magento2-bridge

Integration module allows to integrate Pimcore platform with Magento 2

3513.7k](/packages/divante-ltd-pimcore-magento2-bridge)[divante-ltd/pimcore-translation-bundle

Pimcore Translation Bundle

103.9k](/packages/divante-ltd-pimcore-translation-bundle)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
