1C integration and custom solutions

1C Integration with MAX and Chatbots

A bot over 1C suits short actions: checking a status, receiving an alert, approving a request, or submitting a reading.

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

A bot over 1C suits short actions: checking a status, receiving an alert, approving a request, or submitting a reading. I keep business logic independent from Telegram, MAX, and VK and connect each through an adapter.

Scope includes user identity, permitted commands, the 1C API, a message queue, logs, and channel-specific behaviour. Acceptance ensures another user cannot see the object, repeated buttons cannot repeat an operation, temporary failures follow the agreed delivery rule, shared scenarios work in every stated channel, and tokens remain outside code.

Acceptance criteria

Done when

  • Agreed entities sync with externalId and no duplicates on retry
  • Exchange journal shows object, result, and attempt
  • Failure paths are visible to operators

Deliverables

  • API/contract notes + mapping table
  • Staging exchange runbook

Out of scope

  • 1C accounting-policy changes
  • Production 1C upgrades without change windows

Assumptions

  • Test infobase and a 1C contact for metadata

The final acceptance checklist is confirmed in the brief or contract; the list above is a scope alignment guide.

Ballpark estimate

Scope size
Extras

FAQ

Tap a question to expand the answer.

Can one codebase serve every messenger?

Shared domain logic can. Buttons, authentication, payments, and message formats still require channel adapters and tests.

Can a bot approve 1C documents?

Yes, for a narrowly defined action with identity, role, and document-state checks—not as a universal remote 1C client.

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

View full service page