Adding leads by the database by json

find the label

get the sanbox ui

get the json

process the json

fill the db

send updates on quarterly basis

https://portal.azure.com/#@pexabo.com/resource/subscriptions/ad744a08-2411-4d78-b417-1f1c83f4f741/resourcegroups/ContractorMarketing/providers/Microsoft.Logic/workflows/contractormarketing-savelead-bygmaillabel/logicApp

adding leads by 1

Sandbox Reference

https://developers.google.com/gmail/api/reference/rest/v1/users.messages/list?apix_params=%7B%22userId%22%3A%22info%40pexabo.com%22%2C%22labelIds%22%3A%5B%22Label_1452878502214202942%22%5D%7D

base structure4

adding leads by 2

premise As long as i have the data i can iterate in it to get the necessary parts to do the marketing > email and region are important

Contracting > requires realtime marketing

this has to be send in 24 hour frame

adding leads by 3

add the sandbox reference in here

adding leads by 4

if there is a control in save leads than it is ok to use it

adding leads by 5

there is a check system in there

adding leads by 6

processed

adding leads by 7

have a report to see the number for today

add a todaycount parameter

adding leads by 8

Sell logic apps and write the logic apps

In a transactional world where i sell the devops.engineering service product I got to make sure on the transactional sales process and move the leads to the archieve state on an ongoing basis

adding leads by 9

https://www.canva.com/design/DAF6_YNeh4Q/Eqrjy6nK_gkn-1UBxmoarg/edit?utm_content=DAF6_YNeh4Q&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton

adding leads by 10

Part of the action is the business model ^^^ connected the dots over there >>> areas of emphasis on the work why i do it and how i connect it.

Todays work has to be seen easily >>> not classical crm based but ai based workflow based one and the connection is we are using this to get better and we are selling this for the enterprise integration we get better at sales and package the sales effort. Sales (daily logic app)> borrow (learn for future )> spend ( pay azure ) > package ( in devops engineering on what you learned )

adding leads by 11

Goal is to stack the deck for your favour so when you go in you can sell the on demand delivery as there is training and framework in your hand that is active implementation power is there to lead the team

Today copy paste was direct many eporting titles can come in > could increase the tech debt on the logic app implementation costs

adding leads by 12

Too many logic apps coming in the background for this

adding leads by 13

Count comes up in Zero from yesterday

adding leads by 14

Add debugger inside make it practical run and see the report

adding leads by 15

save lead

adding leads by 16

adding leads by 17

Check the parameter and check the report

Save looks ok

adding leads by 18

one is here

adding leads by 19

Numbers rising that is good news at least we are moving in the correct direction

adding leads by 20

todo >> the miro board needed to make sense of the logic apps and they are working and they are usefull

Count 3 is coming for the day at least i can understand i am working

adding leads by 21

this is not a practical CRM ui based app this is a database based CI/CD based application where i am bulindg a sales machine for the recruiters to support contracting and than i would be able to use the know how in the devops.engineering product.

Second run i expect to see 3 not 4

adding leads by 22

Now it looks like it is working still unlikely the 58 leads did not get added to the system>>> check one by one >

[email protected]

adding leads by 23

Many use cases comes up

adding leads by 24

Side backups are the good part of the applications

adding leads by 25

odata query language is needed

adding leads by 26

yesterdays records are not there

adding leads by 27

in one mine it did not get saved

adding leads by 28

save operation is problematic

adding leads by 29

Email content and recuiter is getting pushed

adding leads by 30

These have a problem

adding leads by 31

Daniel did not get inserted

adding leads by 32

Parameter send inside is not daniel

adding leads by 33

https://portal.azure.com/#view/Microsoft_Azure_EMA/LogicAppsMonitorBlade/runid/%2Fsubscriptions%2Fad744a08-2411-4d78-b417-1f1c83f4f741%2FresourceGroups%2FContractorMarketing%2Fproviders%2FMicrosoft.Logic%2Fworkflows%2Fcontractormarketing-saveleads%2Fruns%2F08584953272716785759570286433CU08

Error parameter shouold only be used at the top and self runners not inside only use the variables.

Design patterns hittim me

adding leads by 34

Foixed the paramater to the variable now 3 has to be 30 and than i can remove the old labels and rerun it

adding leads by 35

Runid > not in the link last one is there https://portal.azure.com/#view/Microsoft_Azure_EMA/LogicAppsDesignerBlade/id/%2Fsubscriptions%2Fad744a08-2411-4d78-b417-1f1c83f4f741%2FresourceGroups%2FContractorMarketing%2Fproviders%2FMicrosoft.Logic%2Fworkflows%2Fcontractormarketing-savelead-bygmaillabel

CU18 needs to be there > https://portal.azure.com/#view/Microsoft_Azure_EMA/LogicAppsMonitorBlade/runid/%2Fsubscriptions%2Fad744a08-2411-4d78-b417-1f1c83f4f741%2FresourceGroups%2FContractorMarketing%2Fproviders%2FMicrosoft.Logic%2Fworkflows%2Fcontractormarketing-savelead-bygmaillabel%2Fruns%2F08584953225080416604663588348CU18

With saves runtime moves to 4 minutes from 1 minute

adding leads by 36

47 inserts

adding leads by 37

Find a way to look at last 5 entries

contractormarketing-report-leadslastfive

Can see the last 5 maybe the emailid can be added

adding leads by 38

can not see the email text > for future information that is missing

adding leads by 39

The emails with more apps should be able to update the data as well.

email content not send there

adding leads by 40

it should be there but the issue is the header should have a size blocker

adding leads by 41

Move it to the body

Packaged ui based product versus datasource based actions are very different

adding leads by 42

I have a decision i can rerun and force an update >>> or forget it.

now i would do it as i need to test update function as well

As this function would be run for sometime

adding leads by 43

I would make the system easier for the ai to process make a bigger database >>> make sure i have enough leads to work on on a proactive manner.

Last 5 minute update count needed

adding leads by 44

syntax matters

adding leads by 45

https://stackoverflow.com/questions/64216759/date-comparison-in-azure-logic-app-get-entities-connector

updates to be shown

adding leads by 46

All powers are in the sales cycle to start

adding leads by 47

update should be in the save

adding leads by 48

update is on the left handside

adding leads by 49

email content updates it

adding leads by 50

now waiting for 5 minutes17;20 expect to see the emailbody in the database

adding leads by 51

in the future the ai can process and map in a better fashion !

Also creating the email lists would help the process of getting leads.

Now data incoming it is enough for now

adding leads by 52

multi ones are inside

adding leads by 53

What can i do >>> write a query to detech the doubles

unlimited sales work is there to do

adding leads by 54

adding leads by 55

There are some 2 ones

adding leads by 56

Iterate on them and delete the old one move the data to the new one.

dublicate is the

adding leads by 57

Find the ones to be deleted

adding leads by 58

disable as it cant be reused that easily

add a unique field on email make it easier after deletion

adding leads by 59

backup 218 KB

adding leads by 60

BASICS over risky webui

adding leads by 61

adding leads by 62

empty row are blocking the action

adding leads by 63

run this

select * from leads order by recruiteremail

update leads set recruiteremail='[email protected]' where LeadID=3

update leads set recruiteremail='[email protected]' where LeadID=4

update leads set recruiteremail='[email protected]' where LeadID=5

update leads set recruiteremail='[email protected]' where LeadID=6

to run this

ALTER TABLE Leads

ADD CONSTRAINT recruiteremail UNIQUE(recruiteremail);

now the same email cannot be entered to the system >>>> and there is also a varcharmax logs field which would help

now i can remove the old labels and remap the ones

removed the label

adding leads by 64

reprocess the 236 and then resend the emails for the 236 filtered to 50 >>> and now we have a reply system using the sandbox...faster >>>>and making the logic apps better

map the action >>> new emails with existinf recruiters should go to the logs

adding leads by 65