Saving and building
The .agmp project and the .agm module in the Multogram Modules Constructor: saving, recent modules, backups, the Build module window — name, version, author, description, cover, translations, mode requirements — and releasing a new version.
A module has two files with different roles:
| File | What it is | For whom |
|---|---|---|
.agmp — the project | The source: functions, actions, resources. Opened and edited in the constructor | You, the author |
.agm — the module | A sealed build. Installed and run on the Modules tab | Users |
Keep the project
An .agm module can't be unpacked back into a project. Lose the .agmp and you lose the ability to
change the module. Keep projects separately from builds and make backups.
Saving the project
Save Workflow in the top bar, or Ctrl+S. The project name opens the Project menu: new project, recent, open, save, save as. A saved project appears in Recent modules on the Modules Constructor tab — it is opened again from there.
| Saved | Not saved |
|---|---|
| Functions, folders, actions and their parameters | Resource test values |
| Resources, groups, translations and default values | Variable values after tests |
| Test logs |
Autosave and project backups are turned on in the constructor's Settings. Backups help if something goes wrong, but they don't replace saving.
Building the module
The Build module button (the hammer in the top bar) opens the Build module window. On the left is the module's card as it will be seen on the Modules tab; it changes as you fill in the fields.
| Section | Field | What to enter |
|---|---|---|
| Module data | Name | Required. This is the module's name in the library |
| Version | For example, 1.0.0. Raise it with every release | |
| Author | Optional. Together with the name it determines which module gets updated | |
| Description | What the module does — in one or two sentences | |
| Cover | Click or drag an image; 360×200 is recommended | |
| Manage Translations | The name and description in other languages. English is the default | |
| Package contents | — | How many functions, actions and resources the module has. The module form is built from resources at build time |
| Access requirements | — | The Multogram modes the module will require from the user — see below |
Click Build module and choose where to save the file. The Build Result window shows the path to
the finished .agm.
Mode requirements
Telegram actions belong to Multogram modes: sending a message belongs to Mailer, a comment to Comment Bot, joining a channel to Subscribers Booster. The full list is in Telegram.
- In the constructor, actions of modes your account doesn't have are shown grayed out — they can't be added, and a tooltip names the required mode.
- At build time the Access requirements section lists the modes the scenario uses. If you don't have all of them, the module builds, but it won't run for you either.
- For the user, the module installs and runs only if their account has all these modes — through a plan or bought separately.
Logic, data, file and network actions, as well as signing in to an account (Start Session), don't require modes. A module without mode actions works on any account with the Pro or Max plan.
A new module version
- Open the
.agmpproject, make the changes, check them with a test. - Build the module with the same Name and Author and a new Version.
- Give the file to users. When it is added, Multogram recognizes the module and offers to Replace the installed one, showing the version change.
Common questions
Can I give a module to another person?
Yes, hand over the .agm file. To run it, the recipient needs the Pro or Max plan and the modes from the
Access requirements.
Can I look inside someone else's module?
No. The module is sealed: the scenario can't be opened either in the constructor or on the Modules tab.
Why doesn't the build start?
No Name is given, or the constructor lost its connection to the application — the message in the window names the reason. In the second case, close the constructor window and open the module again from the Modules Constructor tab.
Updated
Testing and debugging
How to check a module in the Multogram Modules Constructor: the test point, single and full tests, testing one action, resource test values, the variables and logs inspector, finding the causes of errors.
AI assistant
The AI assistant in the Multogram Modules Constructor: the Ask and Edit modes, what it can do with the scenario and the module form, the account's AI credits, how to give it tasks and check the result.