{"id":31669,"date":"2024-12-19T16:38:23","date_gmt":"2024-12-19T07:38:23","guid":{"rendered":"https:\/\/docs.c-bot.pro\/?p=31669"},"modified":"2026-03-27T19:25:02","modified_gmt":"2026-03-27T10:25:02","slug":"https_receives","status":"publish","type":"post","link":"https:\/\/docs.c-bot.pro\/en\/user_guide\/triggers\/https_receives\/","title":{"rendered":"HTTPS receptions"},"content":{"rendered":"\n

<\/i> Home<\/a> > User guide<\/a> > Triggers<\/a> > HTTPS receptions<\/p>\n\n\n\n

Japanese may be displayed on some pages.<\/p>\n\n\n\n

Introduction<\/h2>\n\n\n\n

HTTPS receptions is available with a paid plan of Single Office or higher.<\/strong><\/p>\n\n\n\n

About HTTPS receptions<\/h3>\n\n\n\n

You can execute the BOT by making a request to the HTTPS reception endpoint.<\/p>\n\n\n\n

HTTPS reception trigger list<\/h2>\n\n\n\n

Navigate from the 'HTTPS Receptions' under the 'Triggers' in the global menu.
The list of registered HTTPS reception triggers will be displayed.
You can check the Trigger name, Endpoint, BOT name, and Executor.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/div>\n\n\n\n
\"\"<\/figure>\n\n\n\n

The following functions are available on this screen.<\/p>\n\n\n\n

    \n
  1. Add HTTPS reception triggers<\/a><\/li>\n\n\n\n
  2. HTTPS reception trigger Details<\/a><\/li>\n<\/ol>\n\n\n\n

    Add HTTPS reception triggers<\/h2>\n\n\n\n

    You can create a HTTPS receive trigger by clicking the [Create HTTPS reception] button on the HTTPS Receive Trigger List screen.<\/p>\n\n\n\n

    <\/div>\n\n\n\n
    \"\"<\/figure>\n\n\n\n

    The following operations are available from this screen.<\/p>\n\n\n\n

      \n
    1. Endpoint settings<\/a><\/li>\n\n\n\n
    2. BOT settings<\/a><\/li>\n\n\n\n
    3. Registration settings<\/a><\/li>\n<\/ol>\n\n\n\n

      All settings are saved with the [Register] button.<\/p>\n\n\n\n

      Endpoint settings<\/h3>\n\n\n\n

      Trigger name<\/h4>\n\n\n\n

      Set the name of the HTTPS reception trigger.<\/p>\n\n\n\n

      Filter<\/h4>\n\n\n\n

      You can filter the reception based on the conditions you have set.<\/p>\n\n\n\n

      Conditions<\/h5>\n\n\n\n

      [Source IP address]<\/strong>:Evaluate the access source IP address.
      [Basic authentication]:<\/strong>Evaluate the Basic authentication you have set up.<\/p>\n\n\n\n

      *If Basic Authentication is enabled, you can pass through the Basic Authentication by including the following specification in the URL during the request.
      \u3000\u300chttps:\/\/username:password@<\/mark>hook.c-bot.pro\/event_receives\/\u30fb\u30fb\u30fb\u300d<\/small><\/p>\n\n\n\n

      Behavior on condition match<\/h5>\n\n\n\n

      [Receive]<\/strong>:The request is received and a receipt log is recorded.
      [Execute BOT]<\/strong>:Execute the BOT when a request is received.<\/p>\n\n\n\n

      Behavier on condition mismatch<\/h5>\n\n\n\n

      [Do not receive]<\/strong>:No request will be received, and the reception logs will not be recorded.
      [Do not execute BOT]<\/strong>:This setting can be configured when the 'Do not receive' checkbox is unchecked. If a request is received, the BOT will not be executed.<\/p>\n\n\n\n

      BOT<\/h4>\n\n\n\n
      \u5b9f\u884c\u30ad\u30e5\u30fc<\/h5>\n\n\n\n

      \u5b9f\u884c\u30ad\u30e5\u30fc\u3092\u9078\u629e\u3057\u307e\u3059\u3002<\/p>\n\n\n\n

      \u3010\u4f7f\u7528\u3057\u306a\u3044\u3011\u5b9f\u884c\u30ad\u30e5\u30fc\u3092\u4f7f\u7528\u305b\u305a\u306bBOT\u3092\u5b9f\u884c\u3057\u307e\u3059\u3002
      \u3010\u6700\u5927\u4e26\u5217\u5b9f\u884c\u6570\u3092\u6307\u5b9a\u3011\u3053\u306e\u30c8\u30ea\u30ac\u30fc\u306b\u8a2d\u5b9a\u3057\u305f\u5b9f\u884c\u30ad\u30e5\u30fc\u3092\u4f7f\u7528\u3057\u3066BOT\u3092\u5b9f\u884c\u3057\u307e\u3059\u3002
      \u3010BOT\u8a2d\u5b9a\u306b\u5f93\u3046\u3011BOT\u3054\u3068\u306b\u8a2d\u5b9a\u3057\u305f\u5b9f\u884c\u30ad\u30e5\u30fc\u3092\u4f7f\u7528\u3057\u3066BOT\u3092\u5b9f\u884c\u3057\u307e\u3059\u3002
      \u305d\u306e\u4ed6\u3001\u4f5c\u6210\u3057\u305f\u5b9f\u884c\u30ad\u30e5\u30fc\u304c\u8868\u793a\u3055\u308c\u307e\u3059\u3002
      \ufeff<\/p>\n\n\n\n

      \u203b\u5b9f\u884c\u30ad\u30e5\u30fc\u306b\u3064\u3044\u3066\u306f\u3001\u300c\u5b9f\u884c\u30ad\u30e5\u30fc<\/a>\u300d\u3092\u3054\u89a7\u304f\u3060\u3055\u3044\u3002<\/p>\n\n\n\n

      HTTPS\u53d7\u4fe1\u30c8\u30ea\u30ac\u30fc\u306b\u3088\u308bBOT\u5b9f\u884c<\/h5>\n\n\n\n
      \"\u753b\u50cf\u306b<\/figure>\n\n\n\n

      \u3010\u53d7\u4fe1\u6642\u306b\u5b9f\u884c\u3059\u308b\u3011<\/strong>\u30ea\u30af\u30a8\u30b9\u30c8\u53d7\u4fe1\u6642\u306b\u5b9f\u884c\u30ad\u30e5\u30fc\u3092\u7d4c\u7531\u3057\u3066BOT\u3092\u5b9f\u884c\u3057\u307e\u3059\u3002<\/p>\n\n\n\n

      Enable endpoint<\/h4>\n\n\n\n

      Enable the generated endpoint.<\/p>\n\n\n\n

      BOT settings<\/h3>\n\n\n\n

      Configure BOT execution by HTTPS reception trigger.<\/p>\n\n\n\n

      Target BOT<\/h4>\n\n\n\n

      Select the target BOT.<\/p>\n\n\n\n

      Input data mapping<\/h4>\n\n\n\n

      The value set here will be mapped to the input data of the BOT to be executed on the HTTPS reception trigger.<\/p>\n\n\n\n

      [Initial Value]<\/strong>:The data will not be mapped and will remain at the initial value.
      [Fixed Value]<\/strong>:The values entered as fixed values will be mapped.
      [Header]<\/strong>:The request header will be mapped to the input values.
      [Body]<\/strong>:The request body will be mapped to the input values.<\/p>\n\n\n\n

      <\/td>Text type data<\/strong><\/td>File type data<\/strong><\/td><\/tr>
      Initial Value<\/strong><\/td>\u3007<\/td>\u00d7<\/td><\/tr>
      Fixed Value<\/strong><\/td>\u3007<\/td>\u00d7<\/td><\/tr>
      Header<\/strong><\/td>\u3007<\/td>\u00d7<\/td><\/tr>
      Body<\/strong><\/td>\u3007<\/td>\u3007<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Enable BOT execution<\/h4>\n\n\n\n

      Enable BOT execution by HTTPS reception trigger.<\/p>\n\n\n\n

      Registration settings<\/h3>\n\n\n\n

      By pressing the 'Register' button, you will be redirected to the HTTPS reception trigger list screen, where the endpoint for the HTTPS reception trigger will be generated.<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n

      HTTPS reception trigger Details<\/h2>\n\n\n\n

      You can check the details of HTTPS reception trigger.<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n

      The following operations are available from this screen.<\/p>\n\n\n\n

        \n
      1. Endpoint<\/a><\/li>\n\n\n\n
      2. Edit a HTTPS reception trigger<\/a><\/li>\n\n\n\n
      3. Delete a HTTPS reception trigger<\/a><\/li>\n\n\n\n
      4. Check reception logs<\/a><\/li>\n<\/ol>\n\n\n\n

        Endpoint<\/h3>\n\n\n\n

        Generated endpoint.<\/p>\n\n\n\n

        Edit a HTTPS reception trigger<\/h3>\n\n\n\n

        You can edit HTTPS reception triggers. Please refer to the HTTPS reception trigger registration<\/a> for the editing method.<\/p>\n\n\n\n

        Delete a HTTPS reception trigger<\/h3>\n\n\n\n

        Delete a HTTPS reception trigger.<\/p>\n\n\n\n