0216c4c3ae
- Added services/espocrm.py: EspoCRM API client with Redis support - Added 6 VMH webhook steps for EspoCRM integration: Beteiligte webhooks: - POST /vmh/webhook/beteiligte/create - POST /vmh/webhook/beteiligte/update - POST /vmh/webhook/beteiligte/delete Bankverbindungen webhooks: - POST /vmh/webhook/bankverbindungen/create - POST /vmh/webhook/bankverbindungen/update - POST /vmh/webhook/bankverbindungen/delete All webhook endpoints receive batch/single entity notifications from EspoCRM and emit queue events for downstream processing. Note: Complex sync handlers (event processors) not yet migrated - they require additional utility modules (beteiligte_sync_utils.py, mappers, notification_utils) which will be migrated in Phase 3. Updated MIGRATION_STATUS.md with Phase 2 completion.
Motia III - BitByLaw Backend
Motia Backend-Anwendung powered by the iii engine.
Project Structure
bitbylaw/
├── steps/ # Motia Steps (Business Logic)
├── iii-config.yaml # iii Engine Configuration
├── pyproject.toml # Python Dependencies
└── .venv/ # Python Virtual Environment
Services
- Motia API: Port 3111 (https://api-motia.bitbylaw.com)
- iii Console: Port 3113 (https://motia.bitbylaw.com)
- Streams/WebSocket: Port 3114
Systemd Services
motia.service- Backend Engineiii-console.service- Observability Dashboard
Development
# Install dependencies
uv sync
# Start locally
iii -c iii-config.yaml
Production
Services run automatically via systemd on boot.
# Restart services
systemctl restart motia.service iii-console.service
# View logs
journalctl -u motia.service -f
journalctl -u iii-console.service -f
Deployment
Deployed on: motia.bitbylaw.com
Date: März 2026