proca 1.5.0 → 1.7.2

package/README.md

@@ -12,19 +12,18 @@ One of Proca's standout features is its robust support for coalition campaigns,
 
 ### global installation
 
-  <!-- usage -->
+if you have or plan to have multiple servers (eg. production and staging) or multiple users, you can setup multiple environments. each proca command support a --env <environment> param (optional, 'default' if not specified.
+
+All the examples are using the default environment, add --env=staging if you need to access another server than your default one. By convention, we keep default for production.
+
 ```sh-session
 $ npm install -g proca
-$ proca COMMAND
-running command...
-$ proca (--version)
-proca/1.5.0 linux-x64 node-v20.12.2
-$ proca --help [COMMAND]
-USAGE
-  $ proca COMMAND
-...
+$# if you don't have your API token, generate one
+$ proca user reset --email <your_email> --passowrd <your password>
+$ proca config init --token=<API-token>
 ```
-<!-- usagestop -->
+you can set up the config folder the widget builder will use to store the caches. skip unless you want a different one than the default (your/widget/folder/config). 
+
 
 ### local development
 
@@ -36,31 +35,20 @@ USAGE
    $./proca-cli config add --env=local  --url=http://localhost:4000/api
    $./proca-cli config server --env=local #check if the config is working
    $./proca-cli config user #check if the config is working
-...
+````
 
 you should also use the local proca-api in your [widget generator](https://github.com/fixthestatusquo/proca)
 
-```sh-session
+````sh-session
    $ cd /your/path/to/proca
-   $ npm link proca-api
    $ npm link proca # use the local proca-cli repo
-...
-
-
 ````
 
-### TOPICS
-
-- campaign Handle campaigns
-- org
-- config create setting to access the server authentication
-- widget
-- supporters (counter)
-
 # Commands
 
 <!-- commands -->
 * [`proca action add`](#proca-action-add)
+* [`proca action confirm`](#proca-action-confirm)
 * [`proca action count`](#proca-action-count)
 * [`proca action list [TITLE]`](#proca-action-list-title)
 * [`proca action replay`](#proca-action-replay)
@@ -69,6 +57,7 @@ you should also use the local proca-api in your [widget generator](https://githu
 * [`proca campaign delete`](#proca-campaign-delete)
 * [`proca campaign get`](#proca-campaign-get)
 * [`proca campaign list [TITLE]`](#proca-campaign-list-title)
+* [`proca campaign mtt`](#proca-campaign-mtt)
 * [`proca campaign status`](#proca-campaign-status)
 * [`proca config add [ENV] [HUMAN] [JSON] [CSV] [SIMPLIFY]`](#proca-config-add-env-human-json-csv-simplify)
 * [`proca config folder`](#proca-config-folder)
@@ -83,8 +72,8 @@ you should also use the local proca-api in your [widget generator](https://githu
 * [`proca org add`](#proca-org-add)
 * [`proca org crm`](#proca-org-crm)
 * [`proca org delete`](#proca-org-delete)
+* [`proca org email`](#proca-org-email)
 * [`proca org get`](#proca-org-get)
-* [`proca org join`](#proca-org-join)
 * [`proca plugins`](#proca-plugins)
 * [`proca plugins add PLUGIN`](#proca-plugins-add-plugin)
 * [`proca plugins:inspect PLUGIN...`](#proca-pluginsinspect-plugin)
@@ -95,9 +84,16 @@ you should also use the local proca-api in your [widget generator](https://githu
 * [`proca plugins uninstall [PLUGIN]`](#proca-plugins-uninstall-plugin)
 * [`proca plugins unlink [PLUGIN]`](#proca-plugins-unlink-plugin)
 * [`proca plugins update`](#proca-plugins-update)
+* [`proca service add`](#proca-service-add)
+* [`proca service list`](#proca-service-list)
+* [`proca target add`](#proca-target-add)
+* [`proca template add`](#proca-template-add)
+* [`proca template list`](#proca-template-list)
 * [`proca user get`](#proca-user-get)
+* [`proca user join`](#proca-user-join)
 * [`proca user leave`](#proca-user-leave)
 * [`proca user list`](#proca-user-list)
+* [`proca user me`](#proca-user-me)
 * [`proca user reset [USER]`](#proca-user-reset-user)
 * [`proca user whoami`](#proca-user-whoami)
 * [`proca widget add`](#proca-widget-add)
@@ -111,23 +107,27 @@ USAGE
   $ proca action add [ID_NAME_DXID...] -i <value> --firstname <value> --email <value>
     [--json | --human | --csv] [--env <value>] [--simplify] [-x <value>] [-n <the_short_name>] [--testing] [--optin]
     [--action_type <value>] [--lastname <value>] [--street <value>] [--locality <value>] [--region <value>] [--country
-    <value>] [--utm <value>]
+    <value>] [--utm <value>] [--target <value>] [--subject <value>] [--body <value>]
 
 FLAGS
   -i, --id=<value>             (required) widget's id
   -n, --name=<the_short_name>  name
   -x, --dxid=<value>           dxid
       --action_type=<value>    [default: register]
+      --body=<value>           [mtt] body of the email
       --country=<value>        2-letter country iso code
       --email=<value>          (required) email
       --env=<value>            [default: default] allow to switch between configurations (server or users)
       --firstname=<value>      (required) supporter's firstname
   --lastname=<value>
   --locality=<value>
-  --optin
+      --[no-]optin             Whether the user opts in (default: false). Use --optin to enable or --no-optin to
+                               explicitly disable.
   --region=<value>
   --street=<value>
-  --testing
+      --subject=<value>        [mtt] subject of the email
+      --target=<value>         [mtt] uid of the target
+      --[no-]testing           Run action in testing mode (default: true). Use --no-testing to disable.
       --utm=<value>            utm=campaign.source.medium
 
 OUTPUT FLAGS
@@ -140,6 +140,35 @@ EXAMPLES
   $ proca action add -i <widget_id> --firstname=John --email=john@example.org
 
   $ proca action add -i <widget_id> --firstname=John --email=john@example.org --country=FR custom1=A custom2=B
+
+  $ proca action add -i <widget_id> --firstname=John --email=john@example.org target=715a9580-cfe6-4005-9e23-61a62ddecfea --subject='MTT subject' --body='message MTT'
+```
+
+## `proca action confirm`
+
+Should the supporter confirm the action? it can be set either for all the widgets or an organisation or all the widgets of a campaign
+
+```
+USAGE
+  $ proca action confirm [--json | --human | --csv] [--env <value>] [--simplify] [--org
+    <value>] [--campaign <value>] [--confirm] [--template <value>]
+
+FLAGS
+  --campaign=<value>  campaign collecting the action
+  --[no-]confirm      should the supporters confirm each action
+  --env=<value>       [default: default] allow to switch between configurations (server or users)
+  --org=<value>       organisation collecting the action
+  --template=<value>  template for sending the message
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+
+DESCRIPTION
+  Should the supporter confirm the action? it can be set either for all the widgets or an organisation or all the
+  widgets of a campaign
 ```
 
 ## `proca action count`
@@ -369,6 +398,40 @@ EXAMPLES
   $ proca campaign list %pizza%
 ```
 
+## `proca campaign mtt`
+
+set the mail to target (mtt) params
+
+```
+USAGE
+  $ proca campaign mtt [ID_NAME_DXID] --from <value> --to <value> [--json | --human |
+    --csv] [--env <value>] [--simplify] [-i <value> | -n <the_short_name> | -x <value>] [--template <value>] [--period
+    <value>] [--email <value>]
+
+FLAGS
+  -i, --id=<value>
+  -n, --name=<the_short_name>  name
+  -x, --dxid=<value>           dxid
+      --email=<value>          test email address
+      --env=<value>            [default: default] allow to switch between configurations (server or users)
+      --from=<value>           (required) start date (yyyy-mm-dd)
+      --period=<value>         [default: 09:09-18:18] period of the day (HH:HH-HH:HH)
+      --template=<value>       mtt template to use
+      --to=<value>             (required) end date (yyyy-mm-dd)
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+
+DESCRIPTION
+  set the mail to target (mtt) params
+
+EXAMPLES
+  $ proca campaign mtt -n <test-mtt-campaign>
+```
+
 ## `proca campaign status`
 
 ```
@@ -403,7 +466,8 @@ create setting to access to a server
 ```
 USAGE
   $ proca config add [ENV] [HUMAN] [JSON] [CSV] [SIMPLIFY] [--json | --human | --csv]
-    [--env <value>] [--simplify] [--url <url>] [--token <API-token>] [--folder /var/www/proca]
+    [--env <value>] [--simplify] [--url http://localhost:4000] [--token API-token>] [--email you@example.org] [--folder
+    /var/www/proca/config.example]
 
 ARGUMENTS
   ENV       [default: default] allow to switch between configurations (server or users)
@@ -413,10 +477,11 @@ ARGUMENTS
   SIMPLIFY  flatten and filter to output only the most important attributes, mostly relevant for json
 
 FLAGS
-  --env=<value>            [default: default] allow to switch between configurations (server or users)
-  --folder=/var/www/proca  config folder (in the proca widget generator)
-  --token=<API-token>      user token on proca server
-  --url=<url>              [default: https://api.proca.app/api] url of the proca server api
+  --email=you@example.org                 user email on proca server
+  --env=<value>                           [default: default] allow to switch between configurations (server or users)
+  --folder=/var/www/proca/config.example  config folder (in the proca widget generator)
+  --token=API-token>                      user token on proca server
+  --url=http://localhost:4000             [default: https://api.proca.app/api] url of the proca server api
 
 OUTPUT FLAGS
   --csv            Format output as csv
@@ -465,7 +530,8 @@ create setting to access to a server
 ```
 USAGE
   $ proca config init [ENV] [HUMAN] [JSON] [CSV] [SIMPLIFY] [--json | --human | --csv]
-    [--env <value>] [--simplify] [--url <url>] [--token <API-token>] [--folder /var/www/proca]
+    [--env <value>] [--simplify] [--url http://localhost:4000] [--token API-token>] [--email you@example.org] [--folder
+    /var/www/proca/config.example]
 
 ARGUMENTS
   ENV       [default: default] allow to switch between configurations (server or users)
@@ -475,10 +541,11 @@ ARGUMENTS
   SIMPLIFY  flatten and filter to output only the most important attributes, mostly relevant for json
 
 FLAGS
-  --env=<value>            [default: default] allow to switch between configurations (server or users)
-  --folder=/var/www/proca  config folder (in the proca widget generator)
-  --token=<API-token>      user token on proca server
-  --url=<url>              [default: https://api.proca.app/api] url of the proca server api
+  --email=you@example.org                 user email on proca server
+  --env=<value>                           [default: default] allow to switch between configurations (server or users)
+  --folder=/var/www/proca/config.example  config folder (in the proca widget generator)
+  --token=API-token>                      user token on proca server
+  --url=http://localhost:4000             [default: https://api.proca.app/api] url of the proca server api
 
 OUTPUT FLAGS
   --csv            Format output as csv
@@ -562,7 +629,8 @@ create setting to access to a server
 ```
 USAGE
   $ proca config setup [ENV] [HUMAN] [JSON] [CSV] [SIMPLIFY] [--json | --human | --csv]
-    [--env <value>] [--simplify] [--url <url>] [--token <API-token>] [--folder /var/www/proca]
+    [--env <value>] [--simplify] [--url http://localhost:4000] [--token API-token>] [--email you@example.org] [--folder
+    /var/www/proca/config.example]
 
 ARGUMENTS
   ENV       [default: default] allow to switch between configurations (server or users)
@@ -572,10 +640,11 @@ ARGUMENTS
   SIMPLIFY  flatten and filter to output only the most important attributes, mostly relevant for json
 
 FLAGS
-  --env=<value>            [default: default] allow to switch between configurations (server or users)
-  --folder=/var/www/proca  config folder (in the proca widget generator)
-  --token=<API-token>      user token on proca server
-  --url=<url>              [default: https://api.proca.app/api] url of the proca server api
+  --email=you@example.org                 user email on proca server
+  --env=<value>                           [default: default] allow to switch between configurations (server or users)
+  --folder=/var/www/proca/config.example  config folder (in the proca widget generator)
+  --token=API-token>                      user token on proca server
+  --url=http://localhost:4000             [default: https://api.proca.app/api] url of the proca server api
 
 OUTPUT FLAGS
   --csv            Format output as csv
@@ -616,6 +685,7 @@ DESCRIPTION
 
 ALIASES
   $ proca user whoami
+  $ proca user me
 
 EXAMPLES
   $ proca config user
@@ -777,22 +847,25 @@ EXAMPLES
   $ proca org delete  <organisation_name>
 ```
 
-## `proca org get`
+## `proca org email`
 
-view a org
+Set service, usually email backend for an org
 
 ```
 USAGE
-  $ proca org get [ID_NAME_DXID] [--json | --human | --csv] [--env <value>]
-    [--simplify] [-n <org name>] [--config] [--keys] [--campaigns] [--users]
+  $ proca org email [ID_NAME_DXID] --org <value> --mailer mailjet ses stripe
+    test_stripe system preview webhook supabase smtp [--json | --human | --csv] [--env <value>] [--simplify] [--from
+    <value>]
 
 FLAGS
-  -n, --name=<org name>  name of the org
-  --[no-]campaigns
-      --[no-]config      display the config
-      --env=<value>      [default: default] allow to switch between configurations (server or users)
-  --[no-]keys
-  --[no-]users
+  --env=<value>                                                                 [default: default] allow to switch
+                                                                                between configurations (server or users)
+  --from=<value>                                                                Email address to send from (default:
+                                                                                <org>@proca.app)
+  --mailer=mailjet ses stripe test_stripe system preview webhook supabase smtp  (required) [default: MAILJET] service to
+                                                                                send emails
+  --org=<value>                                                                 (required) organisation running the
+                                                                                service
 
 OUTPUT FLAGS
   --csv            Format output as csv
@@ -801,27 +874,25 @@ OUTPUT FLAGS
   --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
 
 DESCRIPTION
-  view a org
-
-EXAMPLES
-  $ proca org get <name of the ngo>
+  Set service, usually email backend for an org
 ```
 
-## `proca org join`
+## `proca org get`
 
-let a user join an organisation with a role
+view a org
 
 ```
 USAGE
-  $ proca org join -o <org name> [--json | --human | --csv] [--env <value>]
-    [--simplify] [--user <value>] [--role owner|campaigner|coordinator|translator]
+  $ proca org get [ID_NAME_DXID] [--json | --human | --csv] [--env <value>]
+    [--simplify] [-n <org name>] [--config] [--keys] [--campaigns] [--users]
 
 FLAGS
-  -o, --org=<org name>  (required) name of the org
-      --env=<value>     [default: default] allow to switch between configurations (server or users)
-      --role=<option>   [default: campaigner] permission level in that org
-                        <options: owner|campaigner|coordinator|translator>
-      --user=<value>    user email
+  -n, --name=<org name>  name of the org
+  --[no-]campaigns
+      --[no-]config      display the config
+      --env=<value>      [default: default] allow to switch between configurations (server or users)
+  --[no-]keys
+  --[no-]users
 
 OUTPUT FLAGS
   --csv            Format output as csv
@@ -830,10 +901,10 @@ OUTPUT FLAGS
   --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
 
 DESCRIPTION
-  let a user join an organisation with a role
+  view a org
 
 EXAMPLES
-  $ proca org join
+  $ proca org get <name of the ngo>
 ```
 
 ## `proca plugins`
@@ -1126,6 +1197,127 @@ DESCRIPTION
 
 _See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.25/src/commands/plugins/update.ts)_
 
+## `proca service add`
+
+Set service, usually email backend for an org, the specific meaning of each param is dependant on the service
+
+```
+USAGE
+  $ proca service add -o <value> --type
+    mailjet|ses|stripe|test_stripe|preview|webhook|supabase|smtp [--json | --human | --csv] [--env <value>] [--simplify]
+    [--user <value>] [--password <value>] [--host <value>] [--path <value>]
+
+FLAGS
+  -o, --org=<value>       (required) organisation running the service
+      --env=<value>       [default: default] allow to switch between configurations (server or users)
+      --host=<value>      server of the service
+      --password=<value>  credential of the account on the service
+      --path=<value>      path on the service
+      --type=<option>     (required) [default: system] type of the service
+                          <options: mailjet|ses|stripe|test_stripe|preview|webhook|supabase|smtp>
+      --user=<value>      credential of the account on the service
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+
+DESCRIPTION
+  Set service, usually email backend for an org, the specific meaning of each param is dependant on the service
+```
+
+## `proca service list`
+
+list services set for an organisation
+
+```
+USAGE
+  $ proca service list -o <value> [--json | --human | --csv] [--env <value>]
+    [--simplify]
+
+FLAGS
+  -o, --org=<value>  (required) organisation running the service
+      --env=<value>  [default: default] allow to switch between configurations (server or users)
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+
+DESCRIPTION
+  list services set for an organisation
+```
+
+## `proca target add`
+
+```
+USAGE
+  $ proca target add -c <value> --name <value> --email <value> [--json | --human |
+    --csv] [--env <value>] [--simplify] [--external_id <value>]
+
+FLAGS
+  -c, --campaign=<value>     (required) mtt campaign to add the target
+      --email=<value>        (required) email of the target
+      --env=<value>          [default: default] allow to switch between configurations (server or users)
+      --external_id=<value>  external id of the target
+      --name=<value>         (required) name of the target
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+```
+
+## `proca template add`
+
+```
+USAGE
+  $ proca template add -o <value> [--json | --human | --csv] [--env <value>] [--simplify]
+    [--type thankyou|doi|confirm|doi_thankyou|doi_confirm] [-l <locale>] [-n by default  type@language] [-s 'template:'
+    + type]
+
+FLAGS
+  -l, --lang=<locale>                   [default: en] language
+  -n, --name=by default  type@language  name
+  -o, --org=<value>                     (required) organisation
+  -s, --subject='template:' + type      subject
+      --env=<value>                     [default: default] allow to switch between configurations (server or users)
+      --type=<option>                   [default: thankyou]
+                                        <options: thankyou|doi|confirm|doi_thankyou|doi_confirm>
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+```
+
+## `proca template list`
+
+list services set for an organisation
+
+```
+USAGE
+  $ proca template list -o <value> [--json | --human | --csv] [--env <value>]
+    [--simplify]
+
+FLAGS
+  -o, --org=<value>  (required) organisation having the templates
+      --env=<value>  [default: default] allow to switch between configurations (server or users)
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+
+DESCRIPTION
+  list services set for an organisation
+```
+
 ## `proca user get`
 
 fetch the information about a user
@@ -1154,19 +1346,48 @@ EXAMPLES
   $ proca user get
 ```
 
+## `proca user join`
+
+let a user join an organisation with a role
+
+```
+USAGE
+  $ proca user join -o <org name> [--json | --human | --csv] [--env <value>]
+    [--simplify] [--role owner|campaigner|coordinator|translator] [-u <user email>]
+
+FLAGS
+  -o, --org=<org name>     (required) name of the org
+  -u, --user=<user email>  email
+      --env=<value>        [default: default] allow to switch between configurations (server or users)
+      --role=<option>      [default: campaigner] permission level in that org
+                           <options: owner|campaigner|coordinator|translator>
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+
+DESCRIPTION
+  let a user join an organisation with a role
+
+EXAMPLES
+  $ proca user join
+```
+
 ## `proca user leave`
 
 leave a org
 
 ```
 USAGE
-  $ proca user leave --email <user email> -o <org name> [--json | --human | --csv]
-    [--env <value>] [--simplify]
+  $ proca user leave -o <org name> [--json | --human | --csv] [--env <value>]
+    [--simplify] [-u <user email>]
 
 FLAGS
-  -o, --org=<org name>      (required) name of the org
-      --email=<user email>  (required) email
-      --env=<value>         [default: default] allow to switch between configurations (server or users)
+  -o, --org=<org name>     (required) name of the org
+  -u, --user=<user email>  email
+      --env=<value>        [default: default] allow to switch between configurations (server or users)
 
 OUTPUT FLAGS
   --csv            Format output as csv
@@ -1207,6 +1428,34 @@ EXAMPLES
   $ proca user list %pizza%
 ```
 
+## `proca user me`
+
+fetch the information about the current user (based on the token)
+
+```
+USAGE
+  $ proca user me [--json | --human | --csv] [--env <value>] [--simplify]
+
+FLAGS
+  --env=<value>  [default: default] allow to switch between configurations (server or users)
+
+OUTPUT FLAGS
+  --csv            Format output as csv
+  --human          Format output to be read on screen by a human [default]
+  --json           Format output as json
+  --[no-]simplify  flatten and filter to output only the most important attributes, mostly relevant for json
+
+DESCRIPTION
+  fetch the information about the current user (based on the token)
+
+ALIASES
+  $ proca user whoami
+  $ proca user me
+
+EXAMPLES
+  $ proca user me
+```
+
 ## `proca user reset [USER]`
 
 Reset user API token
@@ -1256,6 +1505,7 @@ DESCRIPTION
 
 ALIASES
   $ proca user whoami
+  $ proca user me
 
 EXAMPLES
   $ proca user whoami

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "proca",
 	"description": "Access the proca api",
-	"version": "1.5.0",
+	"version": "1.7.2",
 	"author": "Xavier",
 	"bin": {
 		"proca": "proca-cli"

package/src/commands/action/add.mjs

@@ -1,6 +1,5 @@
 import { Args, Flags } from "@oclif/core";
 import { error, stdout, ux } from "@oclif/core/ux";
-import OrgGet from "#src/commands/org/get.mjs";
 import Command from "#src/procaCommand.mjs";
 import { gql, mutation } from "#src/urql.mjs";
 import { getTwitter } from "#src/util/twitter.mjs";
@@ -9,6 +8,7 @@ export default class ActionAdd extends Command {
 	static examples = [
 		"<%= config.bin %> <%= command.id %> -i <widget_id> --firstname=John --email=john@example.org",
 		"<%= config.bin %> <%= command.id %> -i <widget_id> --firstname=John --email=john@example.org --country=FR custom1=A custom2=B",
+		"<%= config.bin %> <%= command.id %> -i <widget_id> --firstname=John --email=john@example.org target=715a9580-cfe6-4005-9e23-61a62ddecfea --subject='MTT subject' --body='message MTT'",
 	];
 
 	static args = this.multiid();
@@ -21,8 +21,18 @@ export default class ActionAdd extends Command {
 			description: "widget's id",
 			required: true,
 		}),
-		testing: Flags.boolean({ default: true }),
-		optin: Flags.boolean({ default: false }),
+		testing: Flags.boolean({
+			default: true,
+			allowNo: true, // ✅ enables --no-testing
+			description:
+				"Run action in testing mode (default: true). Use --no-testing to disable.",
+		}),
+		optin: Flags.boolean({
+			default: false,
+			allowNo: true, // ✅ enables --no-optin
+			description:
+				"Whether the user opts in (default: false). Use --optin to enable or --no-optin to explicitly disable.",
+		}),
 		action_type: Flags.string({
 			default: "register",
 		}),
@@ -50,6 +60,9 @@ export default class ActionAdd extends Command {
 			description: "email",
 			required: true,
 		}),
+		target: Flags.string({ description: "[mtt] uid of the target" }),
+		subject: Flags.string({ description: "[mtt] subject of the email" }),
+		body: Flags.string({ description: "[mtt] body of the email" }),
 	};
 
 	create = async (flags) => {
@@ -95,6 +108,16 @@ export default class ActionAdd extends Command {
 			},
 		};
 
+		if (flags.target) {
+			values.action.mtt = {
+				targets: [flags.target],
+				subject: flags.subject || "Test MTT",
+				body: flags.body || "Please ignore, this is a test",
+			};
+			values.action.actionType = "mail2target";
+		}
+		console.log(values.action.mtt);
+
 		const query = gql`
  mutation (
   $action: ActionInput!