This project has been archived by its maintainers, and is no longer receiving any updates.
dfc-customer-sync
将巨懂车新增留资客户同步到大风车 CRM。
大风车认证使用 APP_KEY 动态换取 dfcToken。同步前会从
danube-tenant-web.souche.com/staffs/all.json 拉取当前门店员工，筛选
roleNames 含“销售员”的记录，并将其 id 用作客户“销售”字段的
recordId。巨懂车的当前跟进人按精确名称或唯一包含关系匹配销售员名称；
同名销售不会自动映射，需通过 dfc.follower_mapping 手动配置。
首次使用：
dfc-sync --setup
dfc-sync --check
dfc-sync
--setup 仅保存巨懂车浏览器登录态。运行同步前需设置 APP_KEY 环境变量。
1 maintainer
Metadata
1 maintainer
Release files for dfc-customer-sync 3.6.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| dfc_customer_sync-3.6.18.tar.gz | 42.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dfc_customer_sync-3.6.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.3 kB
Release files / dfc_customer_sync-3.6.18.tar.gz
| Download URL | dfc_customer_sync-3.6.18.tar.gz |
|---|---|
| Size | 42.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2403292a3932fb605405118bc77e03aa36727ce0c1539e824fe086c6456aedcc
|
|
BLAKE2b-256 checksum How to use checksums |
82a6146b76fea732975a9e55c058c7d3fe74a9cc821751d63d93baecddc133f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / dfc_customer_sync-3.6.18-py3-none-any.whl
| Download URL | dfc_customer_sync-3.6.18-py3-none-any.whl |
|---|---|
| Size | 45.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
40659078d6ae6a211436486aa1e120a6bb589fee0617136e6815155267a8670b
|
|
BLAKE2b-256 checksum How to use checksums |
eedf921c97cdb28b7431ea13859f1ec5526f689bd19fce44f1021d369125b092
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for dfc-customer-sync 3.6.18
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
