HTTP requests: Sending group messages (applicable for external groups)

HTTP requests: Sending group messages (applicable for external groups)

4 min read
📌
Capabilities: Use a bot to send customized card messages or messages containing graphics to groups.
Applicable scenarios: Sync sales data, customer follow-up information, meeting recaps, etc.
Pain points addressed
  • Syncing information manually is inefficient and error-prone 👉🏻 With HTTP requests, messages are sent out automatically to groups and members you specify.
  • Sending updates manually is slow and labor-intensive 👉🏻 With HTTP requests, any changes in information are automatically synced, with the ability to customize the message content.
  • Using plain messages for syncing information lacks differentiation and appeal, leading to low readability 👉🏻 With customizable layouts and types for card messages, you can make use of graphics to create more compelling messages.
Capabilities
  • Send messages at regular intervals: Automatically send a summary to the group at a set time every day, week, month, or another timeframe.
  • Auto-sync new information: When new information is added to a table, the bot automatically sends the new information to the group.
  • Auto-sync updates: When information is updated, the bot automatically sends the update to the group.
Steps
Preparation: Add a custom bot to the group
  1. In the group that you need to send messages to, go to Settings > BOTs > Add Bot > Custom Bot to add a custom bot.
250px|700px|reset
image.png
  1. Configure the bot and obtain its webhook URL.
250px|700px|reset
Scenario 1: Auto-sync new information
  • Applicable scenario: Sync newly added business opportunities every day and assign people to follow up in a timely manner.
  • Process: Members fill out details about the business opportunity in a form and submit it. The bot automatically syncs the information to the group.
  • Steps:
Settings
Details
Screenshot
Trigger: When adding a new record
Note: We recommend using a form to add a new record.
/
250px|700px|reset
Action to perform: HTTP request
Method: POST
250px|700px|reset
Request URL: The custom bot's webhook URL
Request body: raw
  1. Set the card type and copy the card code from the open platform.
  1. Enter the copied code into the highlighted area on the right, then copy the entire code into the request body.
{
"msg_type": "interactive",
"card":the content copied from the open platform
}
Response body: JSON
/
Response value
{}
Scenario 2: Auto-sync updates
  • Applicable scenario: Sync sales report data and customer confirmations with other team members.
  • Process: When a customer's progress changes to Confirmed, a card message is sent to the group.
  • Steps:
Settings
Details
Screenshot
Trigger: When a record changes
Under Select any of fields, select Progress and set Changes to is Confirmed.
250px|700px|reset
Action to perform: HTTP request
Method: POST
250px|700px|reset
Request URL: The custom bot's webhook URL
Request body: raw
  1. Set the card type and copy the card code from the open platform.
  1. Enter the copied code into the highlighted area on the right, then copy the entire code into the request body.
{
"msg_type": "interactive",
"card":the content copied from the open platform
}
Response body: JSON
/
Response value
{}
Scenario 3: Send messages regularly
  • Applicable scenario: Sync customer summaries on a daily, weekly, or monthly basis.
  • Process: Set a time for sending messages to the group every week.
  • Steps:
Settings
Details
Screenshot
Trigger: At scheduled time
Set trigger time: Select the send date and recurrence.
250px|700px|reset
Action to perform: HTTP request
Method: POST
250px|700px|reset
Request URL: The custom bot's webhook URL
Request body: raw
  1. Set the card type and copy the card code in the open platform.
  1. Enter the copied code into the highlighted area on the right, then copy the entire code into the request body.
{
"msg_type": "interactive",
"card":the content copied from the open platform
}
Response body: JSON
/
Response value
{}
Tip: Check the delivery status
If you want to check whether the HTTP request was sent successfully, or if you want to know the details and reasons for why a request couldn't be sent, you can add an action to be performed as the last step of the automated workflow.
Settings
Screenshot
Add a field to the grid to record the delivery status of the HTTP request.
250px|700px|reset
Click Add action > Update record
250px|700px|reset
Select record > Record updated/added/triggered in step 1
250px|700px|reset
Set record content > Select field > Select the field you just added for recording the send log.
250px|700px|reset
Click + > Results from previous actions, and select Response from step 2
250px|700px|reset
Save and activate the automation. You'll then be able to see details about each HTTP request sent.
250px|700px|reset
Written by: Lark Help Center
Updated on 2024-09-05
How satisfied are you with this content?
Thank you for your feedback!
Need more help? Please contact Support.
0
rangeDom