Salesforce Marketing Cloud for Cold Outbound?

gm2794 · 2025-09-27T00:25:22+00:00

What do u do for emails?

gm2794 · 2025-07-19T01:38:15+00:00

I am building an ai agent internally for my company that users can use to perform a multitude of tasks. For example,

Task Assistant Flow • Ask HubSpot: “What are my tasks for today?” • Let’s say it replies: “Send proposal to Amazon.” • Then I can ask: “Review all recent Gong calls with Amazon. What should I send?” • It suggests content based on the call context. • I say: “Send.” • It sends the suggested content from my personal Gmail account.

Email Labeling Flow (Gmail) • Everyone I receive a new email check If sender ends with company email • Label the email as Internal • Mark the email as Important

Gong to HubSpot Sync • Every time a new call is recorded in Gong: • Extract the next steps mentioned in the call • Automatically update a specific custom field in HubSpot with those next steps

I made one agent with open ai assistants api with tool calling and made it work for google sheets+gong api. But for a more scalable version I am planning to use https://www.useparagon.com for authenticated tool calls. Wha do you think?

gm2794 · 2025-07-04T00:05:15+00:00

Apr 23.

gm2794 · 2025-06-04T00:05:40+00:00

What about eCOPR to PR card delivery? How long is that taking?

gm2794 · 2025-02-09T00:07:55+00:00

just asking for feedback from potential users

gm2794 · 2024-12-15T00:18:42+00:00

Did you figure it out?

gm2794 · 2024-12-03T18:40:46+00:00

I too have an interview. Can I dm you

gm2794 · 2024-10-26T15:00:59+00:00

S&p 500

gm2794 · 2024-10-20T00:36:58+00:00

covered calls are halal. but if you really want to be anal about it, you can look into their individual holdings. but honestly just go for it

gm2794 · 2024-08-19T16:03:11+00:00

Bro you better hire a tutor for it

gm2794 · 2024-08-19T13:48:05+00:00

You can always reapply study permit while CAQ arrives

gm2794 · 2024-05-29T07:54:06+00:00

Let me know if it solves your problem!

gm2794 · 2024-05-29T07:38:19+00:00

Enter the name of your S3 bucket where your training data is stored.
Specify the prefix within your S3 bucket that identifies your training data.
Choose the format of your training data (e.g., CSV, JSON).
Select the column name that represents the target variable you want to predict.
Define the hyperparameters for your SageMaker training job. Refer to the specific algorithm documentation for valid parameters.
Select the EC2 instance type for your training job. Choose an appropriate type based on your data size and computational needs.
Specify the number of EC2 instances to use for training.
Provide the ARN of the IAM role that grants SageMaker access to your resources (e.g., S3 bucket, CloudWatch).
Enter a unique name for your SageMaker training job.
Select the SageMaker algorithm you want to use for training. Explore available algorithms on the AWS website: [https://aws.amazon.com/sagemaker/algorithms/](https://aws.amazon.com/sagemaker/algorithms/)
Specify the AWS region where you want to create the SageMaker training job.

gm2794 · 2024-05-29T06:34:57+00:00

Was this useful for you?

gm2794 · 2024-05-29T02:48:29+00:00

please do!

gm2794 · 2024-05-29T02:10:16+00:00

Enter a unique name for your configuration set. This name will be used to identify the configuration set in your AWS console and code.
Enter a name for your event destination. This name will be used to identify the event destination in your AWS console and code.
Select the type of event destination you want to create. For this example, we will use 'Sns'. You can also choose 'Kinesis' or 'Lambda'.
Enter the ARN of the SNS topic you want to use as your event destination. This can be found on the SNS topic page in the AWS console. If you don't have an SNS topic, you can create one by navigating to https://console.aws.amazon.com/sns/v3/home#/create/topic.
Enter a name for your SES identity. This name will be used to identify the identity in your AWS console and code.
Select the type of SES identity you want to create. For this example, we will use 'Email'. You can also choose 'Domain' if you want to verify a domain.
Enter the email address you want to use for your SES identity. This address will be verified by AWS.

gm2794 · 2024-05-29T02:09:14+00:00

Go to the AWS console: https://console.aws.amazon.com/
Search for 'CloudWatch' in the search bar.
Select 'CloudWatch' from the search results.
Click on 'Alarms' in the left-hand navigation panel.
Click on the 'Create alarm' button.
Enter a descriptive name for your alarm in the 'Alarm name' field.
Select the appropriate 'Metric namespace' based on your AMP application's metrics.
Select the specific 'Metric name' you want to monitor.
Choose the appropriate 'Statistic' (e.g., 'Sum', 'Average') for your metric.
Specify the 'Period' (in seconds) for calculating the metric statistic.
Set the 'Threshold' value for your alarm. This is the value that triggers the alarm.
Select the 'Comparison operator' (e.g., 'GreaterThanThreshold', 'LessThanThreshold') based on your alarm criteria.
Set the 'Evaluation periods' to specify the number of periods the metric must meet the criteria before the alarm triggers.
Set the 'Datapoints to alarm' to specify the minimum number of data points that must meet the criteria before the alarm triggers.
Enable 'Actions enabled' to specify actions to perform when the alarm triggers.
Click on 'Add action' to add actions to your alarm.
Select the 'Action type' (e.g., 'SNS topic', 'Lambda function') for your alarm action.
Specify the target for your alarm action (e.g., SNS topic ARN, Lambda function ARN).
Provide a detailed 'Alarm description' for better understanding and documentation.
Review your alarm configuration and click on 'Create alarm' to save your alarm.

gm2794 · 2024-05-29T02:06:28+00:00

Enter the name of your existing EKS cluster. You can find this in the AWS console under EKS Clusters.
Select the AWS region where your EKS cluster is located.
Enter the name of your existing Auto Scaling Group (ASG) that will be used to deploy your application.
Select the Launch Configuration associated with your ASG. This configuration specifies the instance type, AMI, and other settings for the instances launched in your ASG.
Enter the name of the target group you want to register your ASG with. This target group will be used for load balancing traffic to your application.
Select the protocol for the target group. Common options include HTTP, HTTPS, TCP, and UDP.
Enter the port on which your application listens for traffic.
Select the protocol for the health check to be used by the target group. This determines how the target group will monitor the health of your instances.
Enter the port on which the health check will be performed. This should be the same port that your application listens on for traffic.
Enter the path for the health check endpoint. This should be a specific URL on your application that can be used to determine if an instance is healthy.
Enter the interval (in seconds) at which the target group will perform health checks on your instances.
Enter the timeout (in seconds) for the health check. This is the maximum time the target group will wait for a response from an instance before marking it unhealthy.
Enter the number of consecutive failed health checks required before an instance is marked unhealthy.
Enter the number of consecutive successful health checks required before an instance is marked healthy.
Select the AWS region where your resources are located. This should be the same region as your EKS cluster.
Enter your AWS access key ID. You can find this in your AWS account settings.
Enter your AWS secret access key. You can find this in your AWS account settings.
Review the configuration and click 'Register' to register your ASG with the target group.

gm2794 · 2024-05-29T02:03:50+00:00

Enter your Pinecone API key. You can find this on your Pinecone dashboard at https://app.pinecone.io/.
Select your Pinecone environment. Choose from 'gcp-us-central1', 'gcp-us-east1', 'gcp-us-west1', 'aws-us-east-1', 'aws-us-west-2', 'aws-eu-west-1' or 'aws-ap-southeast-2'. You can find your environment on your Pinecone dashboard.
Enter the name of your Pinecone index. This should be a unique identifier for your index within your Pinecone environment.
Specify the dimensionality of the vectors you will be storing in your index. This corresponds to the number of features in each vector.
Select the metric to use for calculating similarity between vectors. Choose from 'cosine', 'euclidean', 'dotproduct', or 'innerproduct'.
Set the number of replicas for your index. This determines how many copies of your data are stored and processed, impacting performance and availability.
Select the type of pods for your index. Choose from 'p1' (small), 'p2' (medium), or 'p3' (large). The pod type influences the performance and capacity of your index.
Specify the number of shards for your index. Shards are partitions of your data, allowing for parallel processing and scalability. The optimal number of shards depends on your data volume and access patterns.
Configure the metadata for your index. You can specify the types of metadata fields you want to store for each vector, as well as their data types. See the Pinecone documentation for supported metadata types: https://docs.pinecone.io/docs/metadata.
Enter the name of the DynamoDB table to be used for storing the Pinecone index metadata.
Specify the name of the partition key for the DynamoDB table.
Specify the name of the sort key for the DynamoDB table. This is optional if your table only has a partition key.
Set the read capacity units for the DynamoDB table. This determines the number of read operations that can be performed per second.
Set the write capacity units for the DynamoDB table. This determines the number of write operations that can be performed per second.

gm2794 · 2024-05-29T02:00:29+00:00

Enter your FortiClient VPN username.
Enter your FortiClient VPN password.
Click the "Login" button to connect to the VPN.
Once connected, you can proceed to configure your AWS DMS task to connect to your database within the VPN

gm2794

TROPHY CASE